On Friday 02 January 2004 2:26 pm, Steve Wampler wrote:
> On Thu, 2004-01-01 at 19:57, Nolan Clayton wrote:
> > Did you try ...
> >
> > tb2.is_shaded_flag := 1
> >
> >
> > without calling the method set_is_shaded()?
>
> Thanks - unfortunately, that doesn't seem to change
> the actual shading on the GUI.
>
> I'm now wondering if I'm misunderstanding how
> events are handled in an ivib-based gui - with the
> above change, I now see the 'changed' and
> 'unchanged' methods called at what I would conside
> odd times.
>
I think what's happening is that you're not distinguishing between the
different event codes which are sent to the buttons - for example the save
button will generate three different codes and handle_saveButton(ev) method
will be called once for each one. The codes are 0 when the button is pressed
down, 1 when it's released (the one which is normally of interest), and -1
regularly whilst it is pressed down (done by a background ticker).
So, just change the handler to something like
method handle_saveButton(ev)
if ev.get_code() = 1 then
unchanged()
end
and it will work okay.
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Unicon-group mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unicon-group
