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 679119 - wrong pre-calculated filesize
wrong pre-calculated filesize
Status: RESOLVED DUPLICATE of bug 669818
Product: GIMP
Classification: Other
Component: General
2.8.0
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2012-06-29 10:01 UTC by P.W.
Modified: 2012-06-29 11:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description P.W. 2012-06-29 10:01:51 UTC
After modifiying and trying to export this picture. The UI calculates a wrong expected file-size. It does not play any role what file-type I try to export. It shows me every time a approximate file-size of ~1.3gb ... 

The real file-size is normal... several hundret kb - depends on the quality i choose.

Than, a quastion:
Will be in further versions a right-click-function in Windows-Explorer implemented where one can choose "Edit with Gimp"... or a direct "Open"-option from Windows-Preview... then right-click on shown picture -> "Edit with Gimp" ?

Or alternatively a own Gimp Galery, so that windows Preview becomes unenessary. In this Galery it would be very important, that one could interprete also professional picture-types like "RAW" etc... 

Until here you all have done very good work. Thank you very much. I am a amateur photographer and use it for about 3 years Gimp together with UFRaw. It becomes more and more a alternative to expensive professional grafic programs. Since 2 years I use only Gimp and I yes, I got the Gimp-Virus - It is a great program!

Best Regards:
Peter
Comment 1 André Klapper 2012-06-29 11:15:33 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 669818 ***