Statistics: Posted by La Tenaille — 25 Aug 2008, 10:20
]]>
antwan
Statistics: Posted by antwan — 19 Aug 2008, 18:42
]]>
Statistics: Posted by senso — 19 Aug 2008, 18:19
]]>
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
Statistics: Posted by antwan — 18 Aug 2008, 08:34
]]>
Statistics: Posted by senso — 17 Aug 2008, 18:05
]]>
Cheers,
antwan
Statistics: Posted by antwan — 17 Aug 2008, 15:12
]]>
i find a work around with the 'initialisation' modul, but it's a bit tricky.
Statistics: Posted by martignasse — 19 Jun 2008, 17:55
]]>
Maybe I should find a solution to provide such possibilities.
Statistics: Posted by senso — 19 Jun 2008, 15:55
]]>
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 ?
Statistics: Posted by martignasse — 18 Jun 2008, 14:29
]]>
]]>
]]>
"A modular construction of interfaces"
That deserves an unprecedented 5 kitties:
->^+^<- ->^+^<- ->^+^<- ->^+^<- ->^+^<-
Statistics: Posted by runagate — 12 Jun 2008, 07:35
]]>
Statistics: Posted by cmodica — 11 Jun 2008, 19:19
]]>
Statistics: Posted by franck — 11 Jun 2008, 14:04
]]>
]]>
it's a good one
Statistics: Posted by martignasse — 11 Jun 2008, 11:34
]]>
It allows a modular construction of interfaces.
Statistics: Posted by senso — 11 Jun 2008, 10:01
]]>