On Jul 18, 2006, at 13:43 UTC, Chuck Pelto wrote: > Seems that the Change event for a TabPanel does considerably more > than merely get triggered when someone clicks on the tabs to change > the panel.
Of course. Chuck, this is true of ALL the events which indicate a change in state. They fire when the state is changed, regardless of whether that change is caused by code or by the user poking at it with mouse or keyboard. The event isn't called "ChangeTriggeredByUser" -- it's just "Change." This is a feature, by design, working as it's supposed to -- when it's not the behavior you want, then simply add a bit of code (as others have suggested) to tell the difference. > I'm getting into a perpetual do-loop by clicking on the tab and > having a specific tab call on a method. The method keeps getting > called again and again and again.... > > In this case a method to populate the cells of a listbox in that > particular tab. > > What's going on here? I couldn't say without seeing it -- but you should be able to tell by pausing it in the debugger and looking at the call stack. You're right, there's nothing in what you've described here that would cause such a loop, so clearly there is something else going on that you haven't yet spotted. But this is why we have a debugger! Best, - Joe -- Joe Strout -- [EMAIL PROTECTED] Verified Express, LLC "Making the Internet a Better Place" http://www.verex.com/ _______________________________________________ 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>
