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 w
On 11/8/2015 7:27 AM, James Hale 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 co
On Nov 8, 2015, at 8:02 AM, Paul Dupuis wrote:
> On 11/8/2015 7:27 AM, James Hale 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.
I've recently started doing this also, for a student/instructor login system.
Depending on who is logging in, some of the input fields and buttons are
different, and there may be multiple steps to the login and registration
process. The main complication is that some buttons and fields need to b
I go completely the other way. I've frequently thought about the many
groups one card method, but I like the mechanics of dealing with the
controls better when I have them over multiple cards (not to mention it's
easier to keep it all straight in my brane). The only time I have multiple
groups on
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 t
Thanks you all for your thoughtful replies.
@Paul Yes this is the direction my thinking has been heading. I think when I
first toyed with this I didn't really find the application browser accessible
(in a meaningful way to me) and thought multiple groups just too messy. But
with the Project Bro
I have a separate group of controls for each tab, and by group I really mean
"group". This way I just have the selectionChanged handler in the tab object
show and hide the corresponding group. In fact I name each group "grp"
so if for example I am showing the sites group:
on selectionChanged pT
