Hi again
working on a new mux right now..
Regarding the Module Slot Editor - when I choose the option to turn off 'include choose/edit/option buttons' and drop a plugin into the slot I cannot open the plugin like I use to with a double click. In fact, I cannot open it at all.
Is this behaviour intended?
Possible issue with Module Slot behaviour
-
- KVRist
- 212 posts since 9 Feb, 2016
Aka Midland Synthetics
-
- KVRAF
- 13891 posts since 24 Jun, 2008 from Europe
I see what you mean.
It's not really intended but atoh i'm transitioning how double-clicks are handled.
MuLab used some special code for it, but i'm working on removing all those cases and purely rely on the standard double-click events reported by the system, for increased compliancy and for avoiding GUI thread complications. This will be better for both MuLab Plugin, which operates in a host context, as for MuLab App on other platforms, eg. Wine/Linux.
Now back to your report: This specific single vs double-click case is a bit difficult case i'm currently struggling with. A single click used to open the module/plugin list, while a double-click used to open the editor. These 2 actions are not very compatible and so to continue the transition to more compliant double-click usage, the legacy behavior might have to change. I've no solution yet, still a work in progress.
Anyway, thx for reporting this.
I'll try to solve this asap during the new M10.3 beta phase.
Question: Why would you like to avoid those module slot side-buttons?
I guess the answer is 'to spare space'.
But then if at some places in MuLab these buttons are there, and at other places not, this may feel inconsistent. I'm just draftly thinking out loud here. Curious for your thoughts on this.
It's not really intended but atoh i'm transitioning how double-clicks are handled.
MuLab used some special code for it, but i'm working on removing all those cases and purely rely on the standard double-click events reported by the system, for increased compliancy and for avoiding GUI thread complications. This will be better for both MuLab Plugin, which operates in a host context, as for MuLab App on other platforms, eg. Wine/Linux.
Now back to your report: This specific single vs double-click case is a bit difficult case i'm currently struggling with. A single click used to open the module/plugin list, while a double-click used to open the editor. These 2 actions are not very compatible and so to continue the transition to more compliant double-click usage, the legacy behavior might have to change. I've no solution yet, still a work in progress.
Anyway, thx for reporting this.
I'll try to solve this asap during the new M10.3 beta phase.
Question: Why would you like to avoid those module slot side-buttons?
I guess the answer is 'to spare space'.
But then if at some places in MuLab these buttons are there, and at other places not, this may feel inconsistent. I'm just draftly thinking out loud here. Curious for your thoughts on this.
-
- KVRist
- Topic Starter
- 212 posts since 9 Feb, 2016
If there was an option to only leave the open plugin icon on the right i'd be very happy to see it. I'm designing a mux which I want to look as clean cut as possibe. So you're right about spare space but its also about aesthetics.
Thanks for getting back to me.
Thanks for getting back to me.
Aka Midland Synthetics