On Jan 3, 2006, at 8:12 PM, John McKernon wrote:
I've been doing it by setting a flag that says "ignore this event",
but it
seems like a really crude way of dealing with it. I'd rather the
event was
never raised. Is there a way of doing this?
That's all you can do. Set a flag to suppress calling Refresh from
ValueChanged and unset it after you've changed the value. Somewhat
painful but the correct way to do it. Other development environments
don't call an event like ValueChanged when you change the value
programmatically (because you already know it changed and it can
cause issues like the one you're having), but REALbasic has behaved
the way it does since the beginning of time and to change it now
would probably break a lot of code. I'm all for that change (it's
better in the long run IMO), but it isn't my choice... <sigh>
Seth Willits
----------------------------------------------------------
Freak Software - http://www.freaksw.com/
ResExcellence - http://www.resexcellence.com/realbasic/
----------------------------------------------------------
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
