Hi Scott,
Could you please give us the version of gtkmm you use: my latest
binaries gtkmm-2.8.8-2 ?
Those problems should have been fixed in the latest release but one
particular case of bad auto-import might have been skipped.
Anyway, if you are really in a hurry for you project, try to add
Do you mean set_cursor()?
Heh. Sorry my bad. I did mean set_cursor().
...and it does not work, sadly. When I specify set_cursor( Path,
Column, true ), it does not force the cell into editing mode, so I
guess I must have just discovered a bug...?
Possibly, but it is working for a lot of
Hi !!
The problem was a codification problem when reading the Glib::IOChannel
codification from a file that was codificate with ISO-8859-15,
extensible too for reading this from a pipe with Glib::IOChannel. The
solution was very simple, with the set_codification(Glib::ustring)
method of
Send Gtkmm-forge mailing list submissions to
[EMAIL PROTECTED]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach
I'm trying to figure out a way to distinguish input from a Wacom Table vs. the mouse, particularly in a on_motion_notify_event signal handler.I've checked everything that looks relevant, but it all seems to be the same device as far as Gtk is concerned.
Specifically, in GdkEventMotion,
However you add widgets to show they are properly and nicely packed in a
window. But they are not affected as soon as you start resizing Window. The
only remedy I've found is to connect method to signal_check_resize() of the
main window:
...
signal_check_resize().connect( sigc::mem_fun(
You might want to
have a look at theGimp source code. It does this for sure. It uses Gtk. So, it
must be possible.
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Paul
DavisSent: Thursday, September 14, 2006 3:44 PMTo:
gtkmm-list@gnome.orgSubject:
On Thursday 14 September 2006 11:27, Javier Aranega wrote:
Hi !!
The problem was a codification problem when reading the Glib::IOChannel
codification from a file that was codificate with ISO-8859-15, extensible
too for reading this from a pipe with Glib::IOChannel. The solution was
very
