by Shrinker on Wed Aug 26, 2009 5:18 am
A only has an effect when there is exactly one brush selected. How about using the undo feature? (Ctrl+Z) Also, you can change that binding on your own in the config. The config's there for reason :P Hint: Keys 1-8 are not bound by default. Thanks for the description of what you did, I'll try recreating the crash with that. :) Minidump: Yes, good idea. Log: Yes, good idea... but blah :P I actually know what invalid std::vector access caused the crash, but the question is how the program could get into that undefined state in the first place. Could have logged a lot, yeah... hmh. Will see :D
Cuts can locally be undone with merges :)
Okay, I think I have an idea now what went wrong. There is a loophole introduced with the grid menu which I didn't consider before :P When you hit a key that is to trigger a function once, e.g. selecting all, then there is usually a check first whether you are currently locked in dragging something around or similar (anything that has a status display on the lower right), and whatever you've been doing is canceled then instead. That basically means you can cancel a move or cut operation at any point by pressing any key. In the grid menu, however, I entirely forgot implementing that logic, so you probably had movement or similar locked in, and performed another operation, such as cloning, without the operation in progress being canceled, essentially doing something that was never supposed to happen and totally messing up the data :D