Move Last Marker and Next Marker buttons from the bottom toolbar to the bottom of the prompter

[Cuperino]

Is your feature request related to a problem or a limitation? Please describe... Limitation. The last and next marker buttons can't be easily accessed while prompting without the use of a keyboard. Having dedicated buttons for this placed before and after the decrease velocity and increase velocity buttons would be very helpful.

Describe the solution you'd prefer Mash wrote:

It would be great to have the following controls (there is plenty of real estate with space in between) while in prompting mode.

Exit … Last Marker … Slower … Start/Stop (Blue Button) … Faster … Next Marker

Request based on forum conversations with user Mash: https://forum.cuperino.com/t/prompting-bar-controls/83

[Cuperino]

It should be noted that, while user Mash wrote "there is plenty of real estate with space in between", the space is only available on his screen because QPrompt is running without up-scaling, on a fairly large resolution that is effectively larger than what would be available on a portrait phone. The proposed solution most likely wouldn't work within a phone's proportions, defeating Kirigami's convergence.

A compromise must be found. Some options are:

• Show the additional 2 buttons only above certain perceived resolutions
• Allow the buttons and their layout to be customizable, with parameters such as controlling width, height, shape, and space in between separately.

The solution must be easy to use and work with any theme QPrompt is configured to use.

[videosmith]

In reference to phones, could the volume buttons or tap feature of air pods be mapped to this purpose"

[Cuperino]

Qt offers means for handling volume inputs and QPrompt is already configured to use the volume keys to control its velocity. Unfortunately the feature doesn't work in most modern OS. It was developed for Nokia phones, back when Nokia owned Qt, and later used in Blackberry's system, QNX, which is still used to this day for embedded devices.

Android removed this ability long ago, to prevent malicious software from intercepting volume controls. There may exist an alternate API to do this, but trying to access Android's APIs from Qt very easily results in crashes.