RFC: UI Layout Changes (Part 1) #398
Replies: 3 comments 14 replies
-
I love this! The transport looks way more usable. I've been writing a feature request https://github.com/tenacityteam/tenacity/issues/399 today for changes to the meters as well. There I propose docking areas on both sides of the window to make vertical meters useful. I've also been thinking about ways to improve the device/channel ui, It's a bit confusing right now imo. It might be a good idea to indicate which is protocol/driver, and which is device. And the channel-count label "recording channels" could easily be interpreted not as number of channels to record, but channel routing, and it's also strange to me to have the label included in the drop down of the first two options. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I spent some time today experimenting with the UI and I explored a couple of different ideas.
The primary idea here is to move the volume indicators on a new bar, while taking advantage of the vast amount of space that's available to us. This obviously isn't final, just a general idea, but it will definitely need a lot of polishing if I were to actually implement something like this (since I only really moved widgets around). I'm sort of skeptical about the concept of sacrificing horizontal screen space in order to make the volume bars more easily readable. I'd like to hear your feedback.
Some ideas haven't been included in the screenshot, as the screenshot depict an actual instance of Tenacity running on top of the master branch (a21a554). They are out of scope for the time being, until I (or someone else) come up with some tangible examples. Some of them include
Beta Was this translation helpful? Give feedback.
All reactions