User Tools

Site Tools


fire_tasks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
fire_tasks [2019/02/27 15:39]
admin [Call Buttons with Hotkeys]
fire_tasks [2019/02/27 16:40]
admin [Call Buttons with Hotkeys vs. Playlist]
Line 51: Line 51:
 Now open the Playlist window, right click on an item and select //Edit Key//. If the Key Capture window opens select the text field to make sure it has the focus. Now press the key on the Stream Deck (I mean the physical device in this case, not the software). The Key is now captured and assigned if you press //OK//. Now open the Playlist window, right click on an item and select //Edit Key//. If the Key Capture window opens select the text field to make sure it has the focus. Now press the key on the Stream Deck (I mean the physical device in this case, not the software). The Key is now captured and assigned if you press //OK//.
  
-==== Call Buttons with Hotkeys ====+==== Call Buttons with Hotkeys ​vs. Playlist ​====
  
-The Stream Deck part is exactly the same then we did in the Playlist example.+As described in the section Call Buttons, we can also assign Hotkeys to buttons. ​The Stream Deck part is exactly the same then we did in the Playlist example. To capture a Hotkey for a button right click the button and select //Change Hotkey//. Now press the key on the Stream Deck and click OK. The caption of the Button changes. It starts with the keyname and a ":",​ followed by the Caption. 
 + 
 +**There is an important difference between the Playlist and the Call Buttons.**  
 + 
 +The Playlist will get the key-press events only if it has the focus. There is an Option to start the Playlist as modal dialog ( In the Main Menu select //​Configure->​Options//​ and check the //Modal Playlist Dialog// checkbox). As modal Dialog you can't access the V-Control window until the playlist is closed. Ifd the Playlist does not have the focus, the key-press event is forwarded to the element that has the focus, and the task that is assigned to the hotkey will not fire. 
 + 
 +For the Call Button Window it is not necessary to have the focus. As soon as the window opens, a process is running that capture all key-press events, even if you type text in an editor for example. You can minimize the window and still the keyboard events will be recognized. 
 + 
 +Depending on what you are doing the Playlist or Call Button method might be better. Keep in mind that in both cases key-press events are send to the element that has the focus. So if, for example, the Hotkey is //F1//, and you have an application running that has the focus, it might show it's help screen. ​   
 + 
 +By the way, it is OK to use both, the Playlist and the Call buttons at the same time. But if the Playlist has the focus, and there is the same Hotkey in the Playlist and in the Call Button window, then the task might be fired twice. That depends on how long the Task is running. If the task runs very short this can happen. If it needs longer, then the second execution will not happen because a running task can not be started again. 
 + 
 +By all this keep in mind that using the [[tcp_connectors#​elgato_stream_deck_connector|TCP_StreamDeckConnector]] is not so convenient, but more secure.
fire_tasks.txt · Last modified: 2019/02/27 16:40 by admin