![]() ![]() I'm thinking of allowing apps to suggest keybindings to be helpful but those still won't be binding on the user. I was about to sleep while writing the previous comment and it the plan is that apps won't be able to force a keyboard shortcut, rather the user gets to choose them. We may also (optionally) consider passing it back to the app in argv/dbus so that if the app allows users to have some custom action on keypress (eg run a series of user defined actions or enter a custom text) it can simply identify against the unique PTT would require sending key-up and key-down flags as distinct signals which isn't something other apps wanna deal with and something we want to avoid sharing unless absolutely necessary.Īnd yes I was thinking of similar structure as screencast API. The app can use that to request current key-binding, or clear it. We store an invisible to user token for each app that has requested a global shortcut. Without 1 & 3, I have a simple structure in mind: I'm on mobile right now, but GSConnect can trigger the action in its own UI, so unless it uses a weird hack, gnome already has most of the stuff in place. It would certainly be easier as except for a portal to trigger the add shortcut UI automatically and pre-filling the command, we already have everything else in place. It was a valid feature to impliment on x after all.Įxcept for the PTT/overlay case, I do think most use cases can be solved by the current shortcut system of just executing a command with a flag/dbus-send to let the app know of an action. I personally don't care either way but just thought this might be something someone might be looking for. But a UI that dynamically changes a lot might wanna use this too. PTT actions are probably a good example of its use case. ![]() In that case, Do we want that to be a seperate API?Īs for the third one, the shortcuts are automatically cleared when you sign out (or quit the app, not really sure which one would be better). Do we want to support that use case? I feel like with the ubiquity of video conferencing these days, there might be a lot of request to support this regardless. That said, I do have a different use case in mind that I glossed over previously - for PTT the app needs to know if the keys are currently pressed or not. I did have a different one in mind a few days ago but I failed to write it down □ so it's lost to history I guess. For one, push to talk and apps that display an overlay/menu when you press and hold apps are the only two use cases I can think of right now. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |