GNOME Bugzilla – Bug 504538
When image is not found, eog shows broken background for the message
Last modified: 2009-03-12 22:12:48 UTC
Please describe the problem: When you try to open a non-existing image, eog displays a message but the background is wrong (see attached screenshot). Steps to reproduce: Just open a file that does not exist (the way I hit this was using the recent documents menu). Actual results: Expected results: Does this happen every time? Other information:
Created attachment 101276 [details] The error message with incorrect background
Confirming. This only happens when using the recent files menu. It works when trying to open a non-existing file from the command line. When I then change the window size the message area will redraw correctly, btw.
I find the inline error dialog is not very sane since we have to deal all theming issues related to that dialog (please excuse me if I am wrong). IMHO, why don't we just have simple pop-up dialog like Mac Image Viewer and Windows Viewer?
Well, I see other redrawing issues as well (drag the rigth border of the window to the right and see the right border of the area being drawn incorrectly.
well, we weren't handling the size allocation. I set up a size_allocation() callback for the "size-allocation" signal to call gtk_widget_queue_redraw(), so that we ensure that the widget is drawn correctly when the size of the window changes (or upon the initial allocation). Fixed in trunk. This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report. 2008-09-05 Claudio Saavedra <csaavedra@igalia.com> * src/eog-message-area.c: (size_allocate), (eog_message_area_init): Enqueue a redraw of the widget upon allocation. Fixes bug #504538.
I noticed some redraw issues on resize, but I think I fixed them all. But thanks for the notice.
One more thing to consider is if we really want to hardcode using the tooltip theming here, or make this widget independently themeable. There's some tricky issues with fallback, though.
*** Bug 575125 has been marked as a duplicate of this bug. ***