After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 412575 - Why specify the user needs to save?
Why specify the user needs to save?
Status: RESOLVED NOTABUG
Product: eog
Classification: Core
Component: documentation
git master
Other Linux
: Normal normal
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on: 322243
Blocks:
 
 
Reported: 2007-02-27 09:21 UTC by Joachim Noreiko
Modified: 2010-09-16 13:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Joachim Noreiko 2007-02-27 09:21:17 UTC
From the manual:
'The modifications are done in memory and alter the original files on disk only when the images are saved with the save function'
'The rotation is not saved until you save the rotated image'

Users are familiar with the concept that changes made to documents aren't saved until they tell the app to save.
Does EOG have actions that break this convention, thus requiring the convention to be stated explicitly?
What users should be warned of however is that EOG doesn't give a warning on closing an image with unsaved transformations. Is this a bug?
Comment 1 Pavel Šefránek 2008-03-09 12:54:19 UTC
This is actual since we will resolve bug 322243
Comment 2 Claudio Saavedra 2010-09-16 13:20:04 UTC
I'm going to close this as NOTABUG, since I don't see any problem with the manual stating this. Other image viewers chose to save the changes automatically, so it's not so obvious that eog is not going to do it.