From the original SynthMaker forum (2004–2014), with its members’ names and dates.
tester ·
Small question, because maybe some of you did this before. I searched the forum but without success (or with wrong keywords). I'd like add a switchable pop-up window over the interface. Clicking a trigger button - opens a window with any content over the main interface, clicking other trigger button - closes that window. As far I understand, it will use mgui connected to the selector element for making it visible, but don't know how to make it invisible again (or just missed something; my brain slowly falls asleep for today).
Second thing - is there an easy way to make that window scrollable, like html documents in browser? I saw on forum, that there are some scorlling lists, but I guess these were limited to textual content only (no controls or "any content" so to speak). It would be useful when adding longer content, like credit lists with graphical data and links, and so on.
loopeytunes ·
Here's one I've just put together from a few modules I got from.....mmmmm.........mmmmmmmmm
I really can't remember hahaha
anyway I hope this is what you want
loopey
tester ·
Thanks!
I just realized, that I can re-use the multiplexer module I worked on (somewhere on this/Help forum), for switching panels. ehhh... I'm still thinking in old terms. 😉
tester ·
For loading popup/setup window - I think I will use this one. It exchanges main window with second window which can contain abouts or setups with controls. Instead of green leds (one per window) - buttons like "open" and "close" can be used.
Now I have to find out, how to add more sub-windows opened that way, i.e. - how to change the led triggers into various integers in order to drive the multiplexer.
tester ·
A small update - easy to configure way for making over-the-interface setup (with knobs and so on), help and other kind of additional open-close windows. Feel fre to use, feel free to optimize 😉
trogluddite ·
The only small change I would make is to send the "which window" value directly to the ReDraw instead of duplicating the wireless trigger links (all "green" data types contain implicit triggers that can be "extracted").
Partly, it just looks a little neater - but the main reason is that it can be hard to control trigger order when using wireless links.
It's important here that the multiplexer "sees" the trigger before the ReDraw does, otherwise the screen will not update correctly. With "visible" links you can see this explicitly (the little 'tick marks' at link nodes). With wireless, it is purely down to the order of creation - so, for example, cutting and pasting modules containing wireless links can alter the trigger order and lead to unintended behaviour.
tester ·
Like this?
Anyway thanks for explaining; I think I had such issue with the multiplexer when it was on the table, and did not see why it not worked; did not see why it started to work after fixing by Mo 😉.
p.s.: re-updated to 2.2
trogluddite ·
tester wrote: Like this?
That's it exactly. 🙂
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker