Interface builder improvements

YouTube · Unread post by **senso** » 11 Jun 2008, 10:01

As you know the interface builder is now (next release) totally WYSWYG and
I have also implemented the concept of 'container': for example you put a subpatch which contains a 'local interface builder'. You can now, put the entire interface of the subpatch in the parent interface (or the global interface window).
It allows a modular construction of interfaces.

martignasse · Unread post by **martignasse** » 11 Jun 2008, 11:34

just can say WOW

it's a good one

bsork · Unread post by **bsork** » 11 Jun 2008, 12:07

WOW is the word!

franck · Unread post by **franck** » 11 Jun 2008, 14:04

BRAVO Olivier
Frank and friends

cmodica · Unread post by **cmodica** » 11 Jun 2008, 19:19

You are definitively the best !!!
Merci

runagate · Unread post by **runagate** » 12 Jun 2008, 07:35

That's... brilliant.

"A modular construction of interfaces"

That deserves an unprecedented 5 kitties:

->^+^<- ->^+^<- ->^+^<- ->^+^<- ->^+^<-

gregh · Unread post by **gregh** » 12 Jun 2008, 12:17

my first post is to congratulate you on this addition (and everything else:) )

nay-seven · Unread post by **nay-seven** » 12 Jun 2008, 12:34

more and more handy ...thats really great...!!

martignasse · Unread post by **martignasse** » 18 Jun 2008, 14:29

Ok,

Now, with the 3.66d interface power up, we have now a very powerful way to manage the interface of our patch (a real widgets tree, in fact).

But one think is difficult for me to understand :
the way the 'show' ans 'auto show' connector of the 'local interface builder' work.

I want to decide when a local interface is shown in it's parent, but when i load my workspace, all children's interfaces are always shown, i can't make them hidden by default.

I believe these connectors are button type, maybe it's better to have them behave like switch ?

any clue ?

YouTube · Unread post by **senso** » 19 Jun 2008, 15:55

actually the "auto show" hasn't any affect when the interface is not as "stand alone".
It means that containers are always visible when you load the patch. So, no way to hide a container at the loading of a patch.
Maybe I should find a solution to provide such possibilities.

martignasse · Unread post by **martignasse** » 19 Jun 2008, 17:55

ok,

i find a work around with the 'initialisation' modul, but it's a bit tricky.

antwan · Unread post by **antwan** » 17 Aug 2008, 15:12

I'm definately suffering from the same phenomenon here as martignasse. Hoping there we could find a solution to this problem. I'm kind of missing the days when the visibility of a VST or an interface was switch based and not trigger based. I.e. you could just feed a 0 into the 'show' inlet and be sure it will be closed - and vice versa.

Cheers,

antwan

YouTube · Unread post by **senso** » 17 Aug 2008, 18:05

I hope I could find a good solution to replace the button by a switch (visible/invisible).
I will solve all our problems

antwan · Unread post by **antwan** » 18 Aug 2008, 08:34

Thanks!

I think it might be a good idea for the visible/invisible also to have an outlet. So you can also only _get_ the information of a window's status.
Make any sense?

br,

antwan

YouTube · Unread post by **senso** » 19 Aug 2008, 18:19

just an info:
the next version will allow a total access to all parameters as inlet/outlet

antwan · Unread post by **antwan** » 19 Aug 2008, 18:42

cool!

antwan

La Tenaille · Unread post by **La Tenaille** » 25 Aug 2008, 10:20

Great new! I'm very interested in a local interface that shows and hides automatically with its related patch

Welcome to %s forums

Interface builder improvements

Who is online

Login • Register