Possible issue with Module Slot behaviour

[FSM77]

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?

[MuTools]

I see what you mean.
It's not really intended, it's a little bug in an ongoing code transition how double-clicks are handled.

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, still looking for a solution.

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, no? I'm just draftly thinking out loud here. Curious for your thoughts on this.

[FSM77]

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.

[MuTools]

Found and implemented a new standard compliant way to differentiate between a pure single-click vs. double-click.
The next M10.3.1 will use this method so to keep the same single/double-click behavior as before.

[FSM77]

Thanks very much

I have another question. I tried to paste special characters from windows' charmap but they won't go into a mux text box. Is this restriction to safeguard cross platform compatabilty?

[MuTools]

MuLab only supports 7 bit ascii text. I know it's low profile, it's how that code originated 20 years ago, but hopefully that's still enough to make music. Theoretically that could be expanded to a modern unicode system, but that's not planned atm; other developments more directly enhancing the musical creativity and workflow will get more priority.

[MuTools]

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.

Fixed in M10.3.1, see viewtopic.php?p=9277272#p9277272

[PelletProject]

MuLab only supports 7 bit ascii text. I know it's low profile, it's how that code originated 20 years ago, but hopefully that's still enough to make music.

That's a bit sad to hear, I have some sample packs from a few South American producers with diacritics in a few samples that MuLab won't let me type or replace with an asterisk in the browser for example. Other times, I'll have symbols like ╠ in a handful of files that won't play on MuLab at all, neither in the browser nor in the composer. This applies to certain other characters in extended ASCII as well.

Otherwise, they play just fine in Media Player and even in other DAWs. I imagine it will probably get more difficult once sample packs start throwing in Emojis for their sample file names.