On September 22, 2010 01:46:17 pm Bart van Andel wrote: > A more complicated version could auto-undo when you first hide a > picture and then immediately show it again, without doing anything in > between. Or even group all successive hide/show actions and remove > combined hide/show actions (as netto this would be the same as doing > nothing to the image). This should be done when the first non-hide/ > show-action is performed. But that is just an optimization step which > probably only makes sense if such history steps would take up lots of > memory, which I guess they don't.
I am not sure if I understand correctly what you mean. I had thought of "grouping" hutory steps. I have also thought of listing history steps (like in a browser's back button), but for this the descriptions in PanoCommand need to be cleaned up (I already cleand a bit), and some more detail about the specific action need to be extracted (maybe from PanoMemento? I'm still studying that part of the code) to be listed. another feature I am looking into is saving the whole history with the project file. Because the outcome of the optimization process is very much dependent from the initial positioning of the images, access to the whole history of the project can be helpful when fine tuning the individual images. Yuv
signature.asc
Description: This is a digitally signed message part.
