On Oct 22, 2010, at 12:46 PM, J. Landman Gay wrote: > On 10/22/10 12:12 PM, Kee Nethery wrote: >> Thanks Andre, but ... > > I know you've figured this out now, but just wanted to add a couple things. > If you click on the tab button, you shouldn't need to set the selected tab at > all, it should be automatic. The only time you'd need to script the > menuhistory is if you want to do it remotely for some reason. For example, I > have a stack that contains two different tab button backgrounds. One tab > navigates to the other background. Because the tab button on the second > background isn't the same one that was clicked in the first background, I > need to script the selected tab when navigating there. > > When scripting it, be sure to lock messages, set the menuhistory, and then > unlock messages. If you don't lock messages you can get into an infinite loop > in some cases. > > For looking up info on tabbed buttons: the button is a type of menu button. > There is brief documentation in the dictionary under the menuhistory entry, > but I agree it isn't much.
thank you. The tool tip on the tool palettes says "Tab Panel" so I assumed that was it's name. Thanks! kee > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution ------------------------------------------------- I check email roughly 2 to 3 times per day. Kagi main office: +1 (510) 550-1336 _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
