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 662393 - Pixel dust in orientation selector
Pixel dust in orientation selector
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: GUI
git master
Other All
: Normal trivial
: ---
Assigned To: Jean Bréfort
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2011-10-21 15:13 UTC by Morten Welinder
Modified: 2011-11-05 13:20 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Possible patch (400 bytes, patch)
2011-11-04 17:11 UTC, Jean Bréfort 		none Details | Review
Real fix. (575 bytes, patch)
2011-11-05 13:20 UTC, Jean Bréfort 		committed Details | Review

Description Morten Welinder 2011-10-21 15:13:44 UTC 
1. Ctrl-1, Alignment
2. Grab and drag green circle up and down

--> parts of "Text" sometimes get left over on top of the current
(correct) text.  Always above, never below.
Comment 1 Andreas J. Guelzow 2011-10-21 20:21:51 UTC 
hmm, I don't see any pixel dust...
Comment 2 Jean Bréfort 2011-11-03 06:07:39 UTC 
I know that, did not find a solution yet (canvas issue).
Comment 3 Jean Bréfort 2011-11-04 17:05:12 UTC 
Morten, if I move the mouse enough rapidly, I also see some pixels below the text. For some reason, parts of the widget that we invalidate is not redrawn by gtk+. The issue might come from GocText, but I don't see anything there. Of course I might miss even the obvious.

One quick fix would be to call gtk_widget_queue_redraw after each rotation change (I tried, it works), but things like that might happen also inside sheets althought despite all my attempts, I could not see anything wrong there, at least with the most recent code.
Comment 4 Jean Bréfort 2011-11-04 17:11:48 UTC 
Created attachment 200698 [details] [review]
Possible patch

It would be better to fix that in the canvas code, anyway.
Comment 5 Jean Bréfort 2011-11-05 13:20:27 UTC 
Created attachment 200748 [details] [review]
Real fix.

We need to invalidate both the old and the new positions. I don't understand how I could miss that.
Comment 6 Jean Bréfort 2011-11-05 13:20:36 UTC 
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.