[DONE in 5.4.3.2 (Quick Navigator)] Alternative aspect ratios
Posted: Tue Aug 16, 2016 4:18 pm
So I got a Nexus 9 which I think is 4:3 and there's letterboxing in G-Stomper. I know this has been discussed before and I agree it is probably preferable to stretching and scaling to fill the screen if that messes up the layout, the aspect ratio of UI elements etc...
But. What about padding? I don't think I would mind some empty space inserted, for example on the main view, above the step sequencer section (under the four other sections). Or just under the step sequencer, or under the "toolbar".
Now you might ask, what would be the benefit of that? Well, on many other views, like the VA-Beast Synthesizer, it's using more than the available space and we have scrolling with a rack metaphor. If the app filled the screen, views that scroll would show more and need less scrolling.
On views with a "piano roll" sequencer grid, the grid could simply expand to use the available space, padding with empty space under surrounding controls. Now we see more of the grid and need to use the octave switch less.
Would this be difficult to implement? Is all of it difficult or only parts like expanding grids? Maybe the other parts could be added first, simply padding the grids for now?
The letterboxing isn't that bad and I can certainly live with it, but I was hoping that this idea of padding wouldn't be too difficult to implement. Even on views without grids or scrolling racks I think it wouldn't hurt to move the letterboxing to inside the application because you're less likely to hit something else if you miss your touch target.
But. What about padding? I don't think I would mind some empty space inserted, for example on the main view, above the step sequencer section (under the four other sections). Or just under the step sequencer, or under the "toolbar".
Now you might ask, what would be the benefit of that? Well, on many other views, like the VA-Beast Synthesizer, it's using more than the available space and we have scrolling with a rack metaphor. If the app filled the screen, views that scroll would show more and need less scrolling.
On views with a "piano roll" sequencer grid, the grid could simply expand to use the available space, padding with empty space under surrounding controls. Now we see more of the grid and need to use the octave switch less.
Would this be difficult to implement? Is all of it difficult or only parts like expanding grids? Maybe the other parts could be added first, simply padding the grids for now?
The letterboxing isn't that bad and I can certainly live with it, but I was hoping that this idea of padding wouldn't be too difficult to implement. Even on views without grids or scrolling racks I think it wouldn't hurt to move the letterboxing to inside the application because you're less likely to hit something else if you miss your touch target.