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 454505 - Allow progress reporting on asynchronous writing.
Allow progress reporting on asynchronous writing.
Status: RESOLVED OBSOLETE
Product: GEGL
Classification: Other
Component: operations
unspecified
Other All
: Normal minor
: Future
Assigned To: Default Gegl Component Owner
Default Gegl Component Owner
Depends on:
Blocks: 520088
 
 
Reported: 2007-07-07 08:44 UTC by Michael Van Dorpe
Modified: 2018-05-22 12:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Progress bar stops (19.38 KB, image/png)
2007-07-07 08:45 UTC, Michael Van Dorpe
Details

Description Michael Van Dorpe 2007-07-07 08:44:59 UTC
Although gnome-scan properly scans pictures for me, the progress window does not indicate when the acquisition is finished. In the attached screenshot, you will see how the window looks when the scan is finished. The final milimeters of the progress bar never get filled.

Other information:
Comment 1 Michael Van Dorpe 2007-07-07 08:45:26 UTC
Created attachment 91344 [details]
Progress bar stops
Comment 2 Michael Van Dorpe 2007-07-07 08:48:27 UTC
Oops... apparently the progress bar does finish eventually; it just takes 35 seconds for the final millimeter of the progress bar to fill.
Comment 3 Étienne Bersac 2007-07-07 09:42:39 UTC
Hi,

Gegl PNG output is not easy to monitor, thus, depending on resolution and image size, it can take a while :S. I may write my own PNG output in flegita (as well as PDF) for a accurate progress monitoring.

Étienne.
Comment 4 Étienne Bersac 2008-02-26 23:45:10 UTC
Hi,

This is a bug related to GEGL that might be fixed sometime in the future. I don't plan to write my own png saving but rather makes an heavier use of GEGL. GEGL may needs some changes in its API to properly handle such progress. Øyvind Kolås knows more about this.

Thanks.
Comment 5 Øyvind Kolås (pippin) 2008-05-17 12:09:48 UTC
The problem is that currently the writing of a file is blocking. Some form of iterable processing callback is needed for operations like writing large buffers to a file, this isn't currently supported by neither the operations api nor how the processing is done by the GEGL core.

The application is probably already doing what it should do when the capabilitiy is added to GEGL and everything will work a bit smoother after that. Another thing that might improve similar usability things are when GEGL gains the capability to do paralell processing.
Comment 6 GNOME Infrastructure Team 2018-05-22 12:02:18 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gegl/issues/2.