summaryrefslogtreecommitdiff
path: root/todo.md
diff options
context:
space:
mode:
authorPietro Gagliardi <[email protected]>2014-05-24 21:28:28 -0400
committerPietro Gagliardi <[email protected]>2014-05-24 21:28:28 -0400
commit32480a65c257354ab8f4ff0c44c3a8240d3c5274 (patch)
treeabdf91c049805af921125401d4265b3693d330f0 /todo.md
parent511f774649fa53f5bf8e3d42bf79e74193c9596a (diff)
Resolved GtkEntry and GtkProgressBar resizing issues; decided from observing how they do padding that worrying about padding is counterproductive for now.
Diffstat (limited to 'todo.md')
-rw-r--r--todo.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/todo.md b/todo.md
index 6d619e3..1691936 100644
--- a/todo.md
+++ b/todo.md
@@ -41,7 +41,7 @@ super ultra important things:
- make sure the preferred size of a Listbox is the minimum size needed to display everything on all platforms (capped at the screen height, of course?)
- same for Area, using the Area's size (this will be easier)
- make sure the image drawn on an Area looks correct on all platforms (is not cropped incorrectly or blurred)
-- when resizing a GTK+ window smaller than a certain size, the controls inside will start clipping in bizarre ways (progress bars/entry lines will just cut off; editable comboboxes will stretch slightly longer than noneditable ones; the horizontal scrollbar in Area will disappear smoothly; etc.)
+- when resizing a GTK+ window smaller than a certain size, the controls inside will start clipping in bizarre ways (comboboxes will just cut off; the horizontal scrollbar in Area will disappear smoothly; etc.)
- check my logs; someone in irc.gimp.net/#gtk+ answered this (or provided an answer)
- see update 18 March 2014 in README
- resizing seems to be completely and totally broken in the Wayland backend