Interface Builder - Tabs?
I run out of space in IB...
If there were a way to "tab" IB, and you could specify IB1, IB2, IB3, etc., that would help me stuff all the goodies in there that I need! Then all you'd need is a way to select which tab you'd like visible.
I seem to recall reading about an alternate IB surface somewhere (creative memory?) but never found out how to use it...
Thoughts?
If there were a way to "tab" IB, and you could specify IB1, IB2, IB3, etc., that would help me stuff all the goodies in there that I need! Then all you'd need is a way to select which tab you'd like visible.
I seem to recall reading about an alternate IB surface somewhere (creative memory?) but never found out how to use it...
Thoughts?
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
Its a good suggestion, but the main pb is to find a way to be able to select the IB target.
in HH3 there is an option 'also visible in IB' o controls. It means that I should create a more complex selector.
I'll think about. Sometime it take times for me to find solutions....
in HH3 there is an option 'also visible in IB' o controls. It means that I should create a more complex selector.
I'll think about. Sometime it take times for me to find solutions....
Olivier Sens
www.brainmodular.com
www.brainmodular.com
+1
YES should be very usefull in live situation with complex workspace.
But i understand that it should be not easy to implement.
Thank you.
YES should be very usefull in live situation with complex workspace.
But i understand that it should be not easy to implement.
Thank you.
I'm in the middle of a few other projects, but I've been thinking that this may be possible today... Or very close....
If your logical groupings are, say, by rack, and each rack could have its own container on the IB, all you would need is the ability to flag all but one of the containers as invisible, with radio buttons or similar.
Just a thought. It might be closer than we think. I'll experiment a bit later.
If your logical groupings are, say, by rack, and each rack could have its own container on the IB, all you would need is the ability to flag all but one of the containers as invisible, with radio buttons or similar.
Just a thought. It might be closer than we think. I'll experiment a bit later.
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
+1 for having a container available per top level rack with toggle visibility in ib option.shawnb wrote:If your logical groupings are, say, by rack, and each rack could have its own container on the IB, all you would need is the ability to flag all but one of the containers as invisible, with radio buttons or similar.
We are quite close. Check out this proof of concept...
*** NOTE: use the newer version in next post...***
http://www.sensomusic.com/forums/uploads.php?file=Tab-Demo.wkp
If the output from the dropdown matches the name of the current rack, the container is made visible on the interface builder, otherwise it is invisible. The dropdown is dynamically built from the names of the first 3 racks in this example.
I was very happy that the 'lock' feature works nicely with this. Only the visible container is editable, making it easy to work on layout.
This will be my working model going forward...
*** NOTE: use the newer version in next post...***
http://www.sensomusic.com/forums/uploads.php?file=Tab-Demo.wkp
If the output from the dropdown matches the name of the current rack, the container is made visible on the interface builder, otherwise it is invisible. The dropdown is dynamically built from the names of the first 3 racks in this example.
I was very happy that the 'lock' feature works nicely with this. Only the visible container is editable, making it easy to work on layout.
This will be my working model going forward...
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
I made this a little more useful & aesthetic:

Here is the tabbed IB workspace template for download:
http://www.sensomusic.com/forums/uploads.php?file=Tabbed-IB-Template.wkp
So you can get pretty darned close today. Limitations are:
- This assumes one patch & one IB tab per rack.
- There is a bunch of code that must be in each patch for it to work.
In an ideal world, I'd like these new tabs to be new 'Where' options, e.g.:
IB Tab 1
IB Tab 2
IB Tab 3
Underneath the normal 'Where' options (invisible, control panel, container, IB, etc.).
With a corresponding module that exposes attributes such as name, color, etc. I.e., remove the two limitations noted above.

Here is the tabbed IB workspace template for download:
http://www.sensomusic.com/forums/uploads.php?file=Tabbed-IB-Template.wkp
So you can get pretty darned close today. Limitations are:
- This assumes one patch & one IB tab per rack.
- There is a bunch of code that must be in each patch for it to work.
In an ideal world, I'd like these new tabs to be new 'Where' options, e.g.:
IB Tab 1
IB Tab 2
IB Tab 3
Underneath the normal 'Where' options (invisible, control panel, container, IB, etc.).
With a corresponding module that exposes attributes such as name, color, etc. I.e., remove the two limitations noted above.
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
Who is online
Users browsing this forum: No registered users and 42 guests
