I think the difference is that you expect an option button to work that way. Menus are something different. Even if a user made a choice before, you wouldn't want to prevent him from making the same choice again.
Is there a way with a tab object to have no selection, that is have none of the tabs selected? If so, then the proper way of implementing tabs for the purpose described is to set the selection for the tabbed group to nothing as the last thing that happens when you go to another card. That way when you come back to the tabs, any selection is in a sense a new selection. Otherwise you will have to fudge the behavior, in which case tabs are purely a visual effect, not a true object as such. Maybe rolling your own is a better way to go. Bob On Jun 6, 2011, at 5:36 PM, Mark Wieder wrote: > Pete- > > Monday, June 6, 2011, 3:31:02 PM, you wrote: > >> It's still that way in 4.6.0. Also note that the menuPick message for >> tabbed menus includes a parameter containing the previous tab selection as >> well as the one just clicked. Wish they'd done that for ALL types of menu >> buttons. > > Wait a minute. *You're* the one who complained that if the menuHistory > of option buttons changed to match the other buttons you'd have to > rewrite a bunch of code. Make up your mind. I'll go reopen the bug > report. > > -- > -Mark Wieder > mwie...@ahsoftware.net > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
