Re: Tk::DynaTabFrame (was "Re: Tk::CanvasRottext ?")

Dean Arnold wrote:

>
> Default is no tabclose button, so just don't specify it. Or set it
> to undef or 0.

Nice. Perhaps you could add that to the pod. Then again, maybe I missed 
it the first time through.

> wrt Multiple tab rows:
>
> In some cases, I agree (esp. multipage dialogs, where the selections
> should really be either a Properties page - any volunteers for that 
> megawidget ? - or a Wizard type solution). But for IDEs with multiple 
> sourcecode pages, the notebook seems the  best way to go. 

My gripe isn't with Tabbed notebooks in general. I think there's 
definitely a use for them. I particularly dislike when I have multiple 
rows, and I select one of the upper tiers, some implementations will 
reorder all the tabs, moving the selected one to the bottom tier. I find 
it disorienting. Other implementations do not shift the tabs around and 
simply change the color
of the selected tab, which I prefer.

> I've also considered another notebook idiom: the little arrow at the 
> right or left margin that shifts  the tabs left/right, using a single 
> tab row...but I've found that
> more difficult to view (always forgetting which source files I've got  
> loaded)

Yep, I'm not a big fan of that scheme either, though I have seen a 
variation of that also has a button that is more like an Optionmenu, and 
displays a menu of all other tabs that cannot be viewed. I prefer that 
to having to scroll through them one-by-one.

Rob
-++**==--++**==--++**==--++**==--++**==--++**==--++**==
This message was posted through the Stanford campus mailing list
server.  If you wish to unsubscribe from this mailing list, send the
message body of "unsubscribe ptk" to [email protected]