you’re right, it is related to the ballon, it hit me right after I finished
the last post on the subject. I enabled baloon and sure enough, it fires in
sync with the second event. If you wait for the baloon to pop, exiting the
widget also generates two events, one of which is also baloon related
(close). If you don’t, just one is emitted. It fires regardless, if ballons
are enabled for the widget or not.
Omitting events wouldn’t help or be to messy, because you may exit the
widget before the baloon event was emitted. So, depeding on how long you
spent in the widget, you may get two or four events per entry/exit.
However, I figured that the event subtype ( cbinfo->event->subtype ) can be
used to distinguish between these.
0 = crossed boundry from outside
1 = crossed boundry from inside
All others are baloon related.
Guess you have new goodie for your next class
Norbert Black <email@example.com> wrote in message
Joe Hezina <> firstname.lastname@example.org> > wrote:
thanks for the reply. The project goes well, thanks. No “glass bottom” -
I guess I can’t cheat, heh > > ?
Well, you can cheat. We’ll all be able to notice, though. >
Got just one more for today:
- New application, standard window
- Create button
- Set Filtered Child Event callback, Ph_EV_BOUNDRY
- just place some printf in the callback and compile and run in debug
You’ll see that event is correctly fired when pointer crosses the
but leave the pointer inside the button and another event will be fired
about two seconds later, on it’s own. Same event type and subtype.
Expected behaviour? If so, why?
Can’t say this for certain (without source diving for which I’ve
not got time just this instant), but I’d bet a small sum that
that’s how the server produces the “the pointer has been sitting
over your widget for a while - do you have balloon help?” cue.
The time sounds about right for the 1.25 seconds that’s
associated with the behaviour.
The way to confirm this would be to build an app that had balloon
help, and a filter callback on the widget with the help – let
the first boundary event through, and discard the second one.
Does the balloon appear or not?
QSSL Training Services