On Oct 14, 2013, at 3:06 PM, kilon <[email protected]> wrote: > Definetly not a regression. If you make a mistake your work is gone, bye bye, > hasta la vista baby. Personally I dont use, or see myself using CMD+L on a > daily basis. Its highly unlikely that I will code in several lines of code > and will want to discard them completely. In 99/100 cases I just slightly > change, edit the code. So we definitely have a different workflow on this > one. > > You are much better coders than me, so I understand you may use that feature > heavily. > > Undo was my first goal too, but trying to understand how undo is implemented > felt like hammering my face on a wall. The amount of spaggetication in the > code is beyond understanding for me, on the 1 hour I invested of finding a > bug fix. So I spent like 50 minutes trying to understand undo, failed > miserably, spent rest 10 implementing the dialog box. And yes I am not very > smart or good coder. > > I will try to take another look at undo today and have another go at this, > but If I found no solution I will leave the fix as it is. Chances are I wont > figure this out, so don't hold your breath. > > Bottom line is that in case of proper software the user should not allowed > to do things that are unrecoverable without a prompt. So not implementing a > fix at all, at least for me is considered very bad. But this is just my > personal opinion. >
I am 100% with you on this :-)
Marcus
signature.asc
Description: Message signed with OpenPGP using GPGMail
