When I modify dash designs I like to create multiple pages, for example to change the colours and layout .
At present I add buttons on the pages to scroll through the pages but this means I have to touch the screen to select the next or previous page.
I purchased a cheap generic bluetooth media remote and would really appreciate if I could use this to scroll through the pages I’ve created, so when I press the next track button on the remote it is mapped in realdash to trigger the next page and the same with previous track mapped to previous page.
I also have a slider on each screen to dim the screen and would like to use the remote to do this, so the volume up mapped to increase brightness and volume down to mapped to dim the tablet.
This would be awsome to work from the remote. I have the same remote for the music player and got an leftover remote from a firetv stick. It would be super to use it in realdash.
I saw this bumped so I’ll add that I use a Ps4 controller on my tablet as I play minecraft on it, but relized quickly that it is not limited to that app and is pretty good imo. The trackpad is pretty handy as the joysticks are not as predictable as u would assume. I wonder if it had a keyboard attachment like Ps3 had.
Good news is that they both work on Android version of RealDash, and you can make a trigger from keypresses to launch actions.
Bad news is that both of these devices report being a full QWERTY keyboard preventing virtual keyboard to appear for text input. It is prevented system wide, not even web browsers open virtual keyboard with either of these devices connected.
So, while its possible to configure triggers to use these buttons, it would require to disable Bluetooth every time you enter text, like trigger/action name.
Also, while testing we noticed that Windows version of RealDash does not handle the media buttons correctly. That will be fixed in next release.
Anyone interested of testing these Bluetooth buttons, here is basic steps of how to make a Trigger from keypress:
Pair Bluetooth media buttons with your Android device
Then in RealDash, either:
Go to ‘Settings->Application->2nd page->Global Triggers & Actions’ to make these work globally with any dashboard
or enter edit mode and tap ‘Triggers’ on bottom menu to create dashboard specific triggers and actions.
On right hand side tap ‘Add’ to create new Trigger.
Enter trigger name, in this example ‘Next Button Pressed’
Go to ‘Trigger Condition’ and tap the default condition ‘if 0 is …’
Tap on Source Input and filter ‘keyb’ to find ‘Keyboard Status’.
Check that condition in the middle is ‘key is pressed’.
After Keyboard Status is selected as Source Input, the right hand side shows ‘SELECT KEY’ option. Tap that one.
A popup will appear with title “Press a key”. Press your media buttons ‘Next’ button.
Close the condition popup.
Now we have a trigger that activates all the time when media button is held down. Next we will make a reset condition so button must be lifted up before trigger can fire again.
Go to ‘Reset Condition’ and tap the default condition.
Tap on Source Input and filter ‘keyb’ to find ‘Keyboard Status’.
Check that condition in the middle is ‘key is not pressed’.
After Keyboard Status is selected as Source Input, the right hand side shows ‘SELECT KEY’ option. Tap that one.
A popup will appear with title “Press a key”. Press your media buttons ‘Next’ button.
Close the condition popup.
Next we will create an action that is launched with this trigger. In this case, ‘Next Page’ for the active dashboard.
Tap on Actions and Add Action
On Actions popup, select ‘New Action’.
Give action a name, like ‘Next Page’
Tap the “Action Type” button and select ‘Next Page’ from action type list.
Tap upper left corner ‘Done’ until all popups have closed.
If this was a dashboard trigger/action, save your dashboard and exit edit mode.
Now you press media button ‘Next’ to change next page on the dashboard. Adding ‘Previous’ is the same steps while selecting different button and action type.
Its quite a lot of steps to map keypresses to actions, after doing it couple of times it takes only a minute or so to configure a button.
