Revision history [back]

It would be good if native Sailfish applications will be able to use the volume rocker for their own actions (or is it already possible? :) ). Thinking about it, the camera app already uses the volume rocker as a shutter.

How it could work

It would be nice if there was a QML interface for grabbing the rocker and mapping application specific actions to the up and down press. Like that, Sailfish applications could easily grab the volume key regardless of what their backend is written in (so that for example Python apps can use the volume rocker without the need to ship C++ code to access some C++ only API).

Also, the rocker should be grabbed by the application only if its window has focus, once the window looses focus, the rocker should automatically revert to system use. Like this, users can easily control system volume even if using an application that grabs the volume keys.

What the volume rocker can be used for in applications

• map zoom in/out
• turning pages
• shutter
• start/stop/pause something
• trigger in a game

And I'm sure many many more. :)

It would be good if native Sailfish applications will be able to use the volume rocker for their own actions (or is it already possible? :) ). Thinking about it, the camera app already uses the volume rocker as a shutter.

How it could work

It would be nice if there was a QML interface for grabbing the rocker and mapping application specific actions to the up and down press. Like that, Sailfish applications could easily grab the volume key regardless of what their backend is written in (so that for example Python apps can use the volume rocker without the need to ship C++ code to access some C++ only API).

Also, the rocker should be grabbed by the application only if its window has focus, once the window looses focus, the rocker should automatically revert to system use. Like this, users can easily control system volume even if using an application that grabs the volume keys.

What the volume rocker can be used for in applications

• map zoom in/out
• turning pages
• shutter
• start/stop/pause something
• trigger in a game

And I'm sure many many more. :)

It would be good if native Sailfish applications will be able to use the volume rocker for their own actions (or is it already possible? :) ). Thinking about it, the camera app already uses the volume rocker as a shutter.

How it could work

It would be nice if there was a QML interface for grabbing the rocker and mapping application specific actions to the up and down press. Like that, Sailfish applications could easily grab the volume key regardless of what their backend is written in (so that for example Python apps can use the volume rocker without the need to ship C++ code to access some C++ only API).

Also, the rocker should be grabbed by the application only if its window has focus, once the window looses focus, the rocker should automatically revert to system use. Like this, users can easily control system volume even if using an application that grabs the volume keys.

What the volume rocker can be used for in applications

• map zoom in/out
• turning pages
• shutter
• start/stop/pause something
• trigger in a game

And I'm sure many many more. :)