diff options
author | Owen Taylor <owt1@cornell.edu> | 1998-03-01 05:11:05 +0000 |
---|---|---|
committer | Owen Taylor <otaylor@src.gnome.org> | 1998-03-01 05:11:05 +0000 |
commit | 9205edae41b7fdcdda29e8a47739c56f34834f0f (patch) | |
tree | 8f2a329df7aaa39bc746eadf55b45c42fe4bf3d2 /TODO | |
parent | d491547e869c5b918e998e1c68449d2d0e742ada (diff) | |
download | gdk-pixbuf-9205edae41b7fdcdda29e8a47739c56f34834f0f.tar.gz |
gtk/gtkentry.[ch] gtktext.c gtkeditable.[ch]
Sat Feb 28 23:58:54 1998 Owen Taylor <owt1@cornell.edu>
* gtk/gtkentry.[ch] gtktext.c gtkeditable.[ch]
Created a new base widget type Editable for the entry and
text widgets, which encapsulates most of the selection and
clipboard handling stuff, plus some common signals.
Changed the Entry widget extensively to support this,
but the interface and appearance should be the same.
Changed the Text widget moderately to support this.
It now supports:
- Selection style cut and paste
- Clipboard style cut and paste
- Emacs style key bindings (~same as Entry)
- Word motion
- "changed" signal
There are definitely still some bugs in the new stuff.
* gtkfilesel.c gtkspinbutton.c testgtk.c: small changes
to fit the new interface more exactly.
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 31 |
1 files changed, 31 insertions, 0 deletions
@@ -57,6 +57,8 @@ Bugs: segfault in malloc -timj + * Change bitfields to guints from enums for C++ ? + Additions: * it might be good to ues stdio and getch() instead of 1-character reads. so one can take advantage of buffering. Currently each read() takes a separate @@ -111,3 +113,32 @@ TODO AFTER GTK 1.0 This will be covered by upcoming themability, raster is working on it. * More work on Documentation + + * Check return values on all calls to XIC[Get/Set]Values + + * Rewrite the interface to the i18n stuff so GTK widgets don't need to + retrieve X values, and so they don't have to know the value of the + XNxxx character constants. + + * The "-geometry" option should be supported + + - Having gdk_init() parse the geometry option. (putting it into + GDK means you can use XParseGeometry() without wrapping it) + + - Add a call gdk_get_geometry() that retrieves the results + in a form like that returned by XParseGeometry() + + - The application then can modify the results (as would gemvt) + then call a routine gtk_window_set_geometry() on whatever + it considers to be its main window. + + - Then in some manner GtkWindow takes that into account when + setting its hints. (Probably it uses the size and position + as the current uposition and usize, and modulates that + be the equivalents of the X flags + + XValue, YValue, WidthValue, HeightValue, XNegative, or YNegative + + ( You'd have to extend gdk_window_set_hints to accept the + window gravity option to get it right. ) + |