[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xwt-patches
Subject:    [patches] tabpane hiding
From:       Emiliano <emile () iris-advies ! nl>
Date:       2003-04-28 6:25:52
[Download RAW message or body]

> > It's an odd approach, having another variable for this. It creates a
> > non-standard naming convention for tabpane that the others don't have
> > for their children.
> >
> > Why not just have the template that's holding the tabpane remove the
> > children of tabpane that you don't want to display and put them in a
> > holding array?
> 
> That's another approach, but that won't allow me to set up something like
> 
> <tabpane>
>    <tab1/>
>    <tab2 show="false"/>
>    ...
> </tabpane>
> 
> Putting stuff in and out of holding arrays also seems like more work. I
> would have used the invisible property of the peer, but that is used in
> the workings of the tabpane, and has no bearing on the tab being shown.

Another benefit of this approach is that I can show/hide tabs 
referring to them with their id. I'm going to do lots of showing and
hiding, and I need the tabs to stay in the order they were added to the
tabpane. If I use a holding array it'd be a lot more effort
re-calculating the right place to put the tab if I want to have it shown
again. I definately think a property steering tabpane visibility would
be easier here.

> Anyhow, I'm not very much attached to either solution. As long as it
> works, it's fine with me.

So it turns out I am somewhat attached to my solution.

Emile

[prev in list] [next in list] [prev in thread] [next in thread]