On 9 January 2014 12:13, Igor Stasenko <siguc...@gmail.com> wrote: > > > > On 9 January 2014 11:27, Marcus Denker <marcus.den...@inria.fr> wrote: > >> >> On 09 Jan 2014, at 11:11, kilon alios <kilon.al...@gmail.com> wrote: >> >> I was the one that worked on CMD+L dialog. I posted my slice here and it >> was discussed. I tried to implement undo, but trying to understand undo was >> a pain in the ass. >> >> >> I reviewed it and you are not to blame: A key combination that *loses >> code* is not acceptable, and as we discussed in the past, this >> change was needed and good. >> >> Yes, and i agreed on that. > My only complaint is that instead of making things work, we reversed it > and made things even worse. > > >> The people who use the (undocumented!) cmd-L can easily get rid of the >> warning by implementing Undo. >> >> how many modern editors document that pressing home key will move cursor > to beginning of line? or pressing cmd-v will paste things from clipboard? > i do not think this is a good criteria to disable feature(s) only because > they either not documented properly or that someone has no idea it exists. >
yes, to be fair, the Cmd-L was not disabled, but *crippled* , enough that its usefulness become very low. because before i knew that i can type any garbage in any editor window and undo all with single keystroke, and now i have to be interrupted with yes/no popup. Can i ask, why consoles do not ask you are you sure you want to face consequences of you pressed ctrl-c? and in same way, i do not remember myself learning about ctrl-c functionality by reading some docs.. i leaned it by interacting with console and pressing random keys and see what happens. > >> Marcus >> >> And yes Igor I am no pro coder, I code like 30 minutes a day max. I am a >> lawyer that tries to become a pro 2d/3d artist. >> I enjoy coding and an IDE that punishes me for my mistakes does not make >> coding enjoyable for me. >> I think maybe an easy solution is to set all modals to a preference >> setting so they can be easily disabled, thus making everyone happy. >> >> Igor I will be frank with you, coders have no idea how to design good >> GUIs. They see GUIs as nothing more than an inconvenience and extra coding >> effort from their part. >> They usually put out the excuse "I am no designer" yet the truth is that >> they dont care because they cant understand the importance of a great GUI >> to the user. Applications like Photoshop are rare example of good GUI >> design. >> >> >> On Thu, Jan 9, 2014 at 12:00 PM, Marcus Denker <marcus.den...@inria.fr>wrote: >> >>> >>> On 09 Jan 2014, at 10:50, Marcus Denker <marcus.den...@inria.fr> wrote: >>> >>> >>> On 09 Jan 2014, at 10:45, Igor Stasenko <siguc...@gmail.com> wrote: >>> >>> >>> >>> >>> On 9 January 2014 10:38, Sven Van Caekenberghe <s...@stfx.eu> wrote: >>> >>>> The history hack did totally not work for end users, many people, >>>> including myself, lost code, often without noticing or understanding it at >>>> first. >>>> >>>> This 'warning, you did not accept' is/was important and solid, if you >>>> want to replace that the solution should be really good - it was not. >>>> >>>> Don't shoot on Nicolai, he tried to fix it, after asking around. >>>> >>>> i'm not shooting anyone, i just sad there is no progress :) >>> and instead even regress, because now i should also answer 'yes/no' when >>> i press >>> cmd-L.. >>> >>> If some people will need to be asked are they really really really >>> fucking sure they wanted to press a key they pressed, each time they >>> pressing the key, why others, who don't need such stupidity should suffer? >>> >>> >>> These are two different issue: >>> >>> 1) CMD-L >>> >>> >>> The real solution is to implement undo for cmd-L... >>> >>> 2) Not asking in general and rely on history. >>> >>> This is a good idea but it needs to *work* >>> >>> Marcus >>> >> >> >> > > > -- > Best regards, > Igor Stasenko. > -- Best regards, Igor Stasenko.
