Hi,
Dongho Shin [EMAIL PROTECTED] writes:
I connected event signal to GtkTextTag widget and examined the results, which were
somewhat odd for me.
The 'GDK_MOTION_NOTIFY' type event handler was called back only after
'GDK_BUTTON_PRESS' or 'GDK_BUTTON_RELEASE' type event handler was.
That
Hi.
I appreciate your kind suggestion, but that seems not to be the proper solution yet.
Hi,
Dongho Shin [EMAIL PROTECTED] writes:
I connected event signal to GtkTextTag widget and examined the results, which
were
somewhat odd for me.
The 'GDK_MOTION_NOTIFY' type event
Hi,
Dongho Shin [EMAIL PROTECTED] writes:
My working platform is Solaris 2.6 / Sun Ultra Sparc 10.
Can it be the source of my problem?
it shouldn't, but unfortunately there are some bugs that are not
triggered on Linux (where most gtk+ developers work on) but show up on
Solaris (and other
Dongho Shin [EMAIL PROTECTED] writes:
I connected event signal to GtkTextTag widget and examined the results, which were
somewhat odd for me.
The 'GDK_MOTION_NOTIFY' type event handler was called back only after
'GDK_BUTTON_PRESS' or 'GDK_BUTTON_RELEASE' type event handler was.
That is,
On Tue, 2002-05-28 at 07:45, Dongho Shin wrote:
Here is a sample test program which shows the problem.
[snip]
The problem is that GtkTextView doesn't send motion-notify events to the
tags at all. Whether this is on purpose or not, I'm not sure...
The solution is to bind the motion-notify
Hi, all.
I connected "event" signal to GtkTextTag widget and examined
the results, which were
somewhat oddfor me.
The 'GDK_MOTION_NOTIFY' type eventhandler
wascalled back only after
'GDK_BUTTON_PRESS' or 'GDK_BUTTON_RELEASE' type event handler
was.
That is, to catch a
