Csound Csound-dev Csound-tekno Search About

[CSOUND-DEV:3875] Re: Resizing Fl_Tabs

Date2004-01-02 17:58
From"gogins@pipeline.com"
Subject[CSOUND-DEV:3875] Re: Resizing Fl_Tabs
In each visible group, one widget can have "resizeable" enabled. This
widget will expand or contract in such a way as to maintain the original
sizes and locations of the other widgets, as nearly as possible. So each
tab panel in your tabs widget (which is a group) should have "resizeable"
enabled. (Only one panel is visible at a time, so they can all have
"resizeable" enabled even though they all belong to the same parent group.)
This should keep the tab labels from growing or shrinking.

============================================
Michael Gogins
gogins at pipeline period com
Irreducible Productions
CsoundVST, an extended version of Csound for programming music and sound
Available at http://sourceforge.net/projects/csound/
============================================


----- Original Message ----- 
From: "John D. Ramsdell" 
To: "Csound Developers Discussion List" 
Sent: Friday, January 02, 2004 12:40 PM
Subject: [CSOUND-DEV:3873] Resizing Fl_Tabs


> The current version of flCsound contains a tabbing group that displays
> either a transcript of a Csound rendering, or plots generated by the
> rendering.  Resizing flCsound does the right thing with one
> exception.  The tabs in the tabbing group change size, when their
> height is supposed to remain unchanged.  How does one allow the
> resizing of the contents of a tabbing group without allowing changes
> to the height of the tabs?
> 
> John
> 

--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

Date2004-01-02 18:20
Fromramsdell@mitre.org (John D. Ramsdell)
Subject[CSOUND-DEV:3876] Re: Resizing Fl_Tabs
"gogins@pipeline.com"  writes:

> So each tab panel in your tabs widget (which is a group) should have
> "resizeable" enabled.

Your advice in good, and after making the change, the tabs do the
right thing.  I've checked in this fix.  Now if only I could sort out
the memory error...

John