bitfocus / companion

Bitfocus Companion enables the reasonably priced Elgato Stream Deck and other controllers to be a professional shotbox surface for an increasing amount of different presentation switchers, video playback software and broadcast equipment.
http://bitfocus.io/companion
Other
1.55k stars 502 forks source link

Real-time keyboard -> variable entry #2148

Closed mark-epstein closed 5 months ago

mark-epstein commented 1 year ago

Is this a feature relevant to companion itself, and not a module?

Is there an existing issue for this?

Describe the feature

I would love to be able to go into a mode in Companion where any entry on a keyboard attached to the system was dumped into a custom variable. Assuming the keyboard was actively being "captured" by Companion, I'd like to, by pressing a button, redirect the keyboard text entry to

Usecases

on-the-fly text changes of buttons, most notably camera presets rudimentary chat function between companion users without leaving the app

Julusian commented 1 year ago

Im not sure about this. It feels like this will mean that companion can be turned into essentially a keylogger. Also, it would only work on the machine where companion was running, not another machine connected to the same web interface. And I dont expect it will be possible to stop the keyboard events reaching whatever application is in focus, so you will need to make sure that whatever you are typing wont be interpreted as anything by whatever is in focus.

I'm not saying no (for now), but there are a lot of questions here that require some serious thought

mark-epstein commented 1 year ago

Yeah, the keylogger risk occurred to me, but could you make it only work if Companion had focus?

I hadn't really thought beyond the computer running Companion itself but I can see that web connected GUIs wouldn't work.

On Fri, Oct 21, 2022, 16:27 Julian Waller @.***> wrote:

Im not sure about this. It feels like this will mean that companion can be turned into essentially a keylogger. Also, it would only work on the machine where companion was running, not another machine connected to the same web interface. And I dont expect it will be possible to stop the keyboard events reaching whatever application is in focus, so you will need to make sure that whatever you are typing wont be interpreted as anything by whatever is in focus.

I'm not saying no (for now), but there are a lot of questions here that require some serious thought

— Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion/issues/2148#issuecomment-1287403635, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATEBQIF5J5ODPVJUMPSPQ6TWEL4D7ANCNFSM6AAAAAARLPG27M . You are receiving this because you authored the thread.Message ID: @.***>