On 09/17/2011 04:37 PM, oliver wrote:
On Fri, Sep 16, 2011 at 02:36:35PM -0700, Eric Gregory wrote:
On Fri, Sep 16, 2011 at 6:27 AM, oliver<[email protected]> wrote:
This sounds like a possible bug in the undo/redo stack. Do you have a
sequence of steps that makes this occur? If so you could file a bug (or just
e-mail, that's fine too).
Hmhhh, it seems the problem occurs, if shotwell was quitted.
When started next, the Undo-hierarchy is not available.
I'm not aware of any other GNOME application that persists the undo
hierarchy across sessions, so I don't think that Shotwell needs to
either. The undo mechanism is not intended to allow you to go back and
revert recent changes to individual photos; it simply allows you to,
well, undo the last step that you did globally (just like in other GNOME
apps). We could conceivably modify Shotwell someday to keep track of
the order of changes you've made to each photo and to revert recent
changes. But if we do implement that, the user interface will probably
not be through Edit->Undo.
We only write changes to disk when you "export" a photo. Did you try
reverting all changes to the photo? Or if you just want to temporarily see
the original photo, you can hold down the Shift key when the photo is open.
Yeah, this works fine.
Thank you for the hint. :-)
If the Undo-hierarchy also could be used after quitting and executing shotwell
again, then this would be nice.
Again, we probably won't implement this as discussed above.
Also, when non-destructive editing is really possible with
shotwell, then saving the editing sequence, instead of the resulting
picture.
With the save eediting sequence, the editing could be done on the fly
from the src pic and with the recipe/editing sequence.
And much space would be saved too, because only the editing recipe must be
saved,
not the whole resulting filr (or files, if many).
Good news -- this is exactly what Shotwell does today!
OK, fine. :-)
The bad news is you can't enable/disable individual steps in the
transformation "recipe" or apply those changes in a batch to other photos.
Not so fine.
This would be really nice.
Well, to be clear you *can* enable/disable individual steps in the
transformation recipe. For example, suppose that you've cropped a
photo, and adjusted its tint, and used the histogram sliders to change
its dynamic range. Shotwell remembers that you've made all these
changes, and you can go back and adjust any one individually afterward.
To disable any of these changes, simply move the associated slider back
to its default position. (Shotwell does not, however, remember the
*order* in which you made changes to each photo.)
The second part isn't as straightforward as it sounds, since photos with
different dimension and color profiles can't use the same underlying
transformation data for certain types of transformations.
Hmhh, but at least for some transformations this would work:
"enhance" the picture and "red eyes removel" for example
couold just be done - independent of the picture size, I think.
When cutting a picture is done, this could maybe be done
via pixel-coordinates, or relative coordinates.
At least the later should also work with pictures of many different sizes.
Such a "recipe" or "workflow" could be tried on a picture, and
applied if it is possible, otherwise not applied, or the user
could be asked, what to do, if a step in this list of editing commands
could not be applied.
Yes - this might be nice to have. This is
http://redmine.yorba.org/issues/2517 .
adam
_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
