Undo notifications rendering problems #297
Comments
|
From davidcapello on November 28, 2013 08:42:28 This is a known issue. Anyway it's good to have it here in the tracker. To fix this problem we need alpha support for ui::Window (compositable windows). It means: a flag that says "this window should be painted with a special background, that special background is all the widgets overlapped by the window", so a double-buffered technique is need in that case. The main problem: we cannot do this until all widgets use onPaint() event. There are widgets that draw directly on ji_screen/Allegro screen when they receive a kPaint message, so we cannot draw those widget in the "temporary background" yet. |
|
From davidcapello on January 05, 2014 18:18:28 Labels: Version-0.9.6-beta1 |
|
From davidcapello on February 02, 2014 20:06:37 Labels: -Version-0.9.6-beta1 Version-0.9.6-beta2 |
|
From davidcapello on February 24, 2014 03:16:57 Labels: -Priority-Medium Priority-Low |
|
From davidcapello on February 24, 2014 05:10:28 Labels: -Version-0.9.6-beta2 Version-0.9.6-beta3 |
|
From davidcapello on March 08, 2014 16:39:17 Owner: --- |
|
From davidcapello on April 09, 2014 18:42:15 Labels: Milestone-1.1 |
|
From davidcapello on April 19, 2014 14:52:37 Fixed. Commits: af4e714 a34d181 Status: Fixed |
|
From davidcapello on July 16, 2014 18:02:54 Labels: -UI-SpriteEditor Component-UI-SpriteEditor |
From DocHoncho@gmail.com on November 27, 2013 01:53:52
What steps will reproduce the problem? 1. Execute any two operations, especially where the second one has a longer undo message than the first (E.g., Draw with pencil, then flip horizontally)
2. Undo both operations What is the expected output? What do you see instead? Undo notification looks like it is being drawn into an uncleared Bitmap/Memory Region. Seems to affect any undo message that is shorter than the previous one, and has been done in rapid succession.
The time factor is especially interesting.
(Note that the image is modified, the bottom notification is a real example of a corrupted message, the one on top is added for comparison) Please use labels and text to provide additional information.
Attachment: Undo Message Glitch.png
Original issue: http://code.google.com/p/aseprite/issues/detail?id=297
The text was updated successfully, but these errors were encountered: