Welcome to %s forums

BrainModular Users Forum

Login Register

Small UI issues

Tell us what you'd like Usine to do
Post Reply
woodslanding
Member
Posts: 1327
Contact:

Small UI issues

Unread post by woodslanding » 01 Sep 2021, 00:39

1. I like the onscreen keyboard. I guess it's not new, but I haven't used it before, I've used the windows keyboard, but that's awkward because I have to leave full screen mode to get at it. But I'm wishing for the option not to show it on textfields in the menu. I find the menu completely unusable from the touchscreen, so any time I'm working with menu items, I have a mouse and keyboard hooked up.

Additionally, I note that with the onscreen keyboard: when editing a value, the text is not selected. So I typically have to delete the existing text before I can begin typing. This seems particularly awkward with an onscreen keyboard. in fact if this didn't happen, I could ignore the issue above. But since the onscreen keyboard deselects the text, it's frustrating regardless of which keyboard I use. So I turn it off when I'm patching. And then it's not available on the gig when I need it.

2. I still wish for a 'show in patch' button somewhere in the right side menu. When I'm in the IB, 75% of the time that's the only reason I open the left side menu at all. (However, I'm delighted to notice when I do open the left menu, my most recent selection has been recognized, so I don't have to right-click it again. Thanks!!!)

3. Can we get recall for the main window size and position? I have to resize the window every time I do any patching.... an odd omission for a program this mature. This is especially annoying when working with polyphony patches that frequently need a restart because of process errors...

4. Is there any reason to have two text editing fields open at the same time? I can't think of a situation where auto-closing one textfield when another is opened would be a problem for the user....

5. If you drag from 'image file' or 'caption font name' from modules, it is not recognized as a text input... it offers value faders, etc.

6. Similarly, if you drag and create a constant from the Height or Width input on a module, it doesn't take the actual value--it assigns a value of zero. This can be a challenge to debug when your component ends up with a size of 0 x 0!

7. Send and receive modules do not resize correctly to show the entire name in many cases. The first character and even more often gets chopped off. It can be hard to tell what the name of the module actually is, especially as I have a naming convention that puts the chan number first. No other type of module seems to have this problem.
busTitleChopped.png
busTitleChopped.png (19.33 KiB) Viewed 33109 times
that's it for now....
Custom Ryzen 5900x MATX build, Win10, Fireface UFX, touchscreen
Custom 2 manual midi keyboard
Usine, Kontakt, Reaktor, Synthmaster, Byome, Arturia, Soundtoys, Unify

Who is online

Users browsing this forum: No registered users and 8 guests