04-20-2015, 03:36 PM
Part of it is the amount of time and effort it takes to make something completely dynamic in both size and functionality versus something whose behavior you can easily control and define. I tried to think about what actions would really need to be on the quick action bar that couldn't already be triggered through touch actions (corners, tops, bottom), and I really couldn't think of a whole lot beyond what I already provided. Having quick access to the metronome, audio player, and auto-scrolling is still important while performance mode is enabled. If people really like the quick action bar and want it to be more configurable, I can certainly dedicate time to this, but I would need to hear enough feedback for it to be worth the effort.
If you are wondering why I couldn't just change it to at least make all of the buttons configurable, the reason is that the long press is essential for changing the settings of the various controls, otherwise this can't be done without a whole lot of taps (including having to disable performance mode if it is on). If I didn't use long press to configure the button actions, then I would need a separate dialog or screen dedicated to configuring the quick action bar, which just means more work (hence why I need buy-in on what users really want and need).
Thanks,
Mike
If you are wondering why I couldn't just change it to at least make all of the buttons configurable, the reason is that the long press is essential for changing the settings of the various controls, otherwise this can't be done without a whole lot of taps (including having to disable performance mode if it is on). If I didn't use long press to configure the button actions, then I would need a separate dialog or screen dedicated to configuring the quick action bar, which just means more work (hence why I need buy-in on what users really want and need).
Thanks,
Mike