In addition to what others have said, another issue can develop with multiple groups on a single card when you have to work with the groups visually. Having dozens (hundreds) of controls present can sometimes make editing challenging. Placing the tabbed groups across multiple cards encapsulates them nicely. But this might be more of an extreme case than yours.
Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 11/8/15, 4:27 AM, "use-livecode on behalf of James Hale" <use-livecode-boun...@lists.runrev.com on behalf of ja...@thehales.id.au> wrote: >Recently there was some discussion concerning the use of hidden groups >with the tab control. An app I am working on currently uses a tab control >with five tabs that currently go to different cards. The cards concerned >all share a number of other controls responsible for about 60% of their >area with the tabbed panel taking the rest. Some of the panels are simply >variations of another (e.g. Simple vs complex search). >I am now wondering whether there would be an advantage in reducing these >five cards down to one and use the hidden group method. >Given I am not starting from scratch my question is, would there be >advantages to me in making this transition? >So for those of you employing this method, why do you? >Is it having a single card script? >Is it keeping the stack structure simple? >Is it...? >I would be very interested in your thoughts. > >James >_______________________________________________ >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
