HOTKEY - problems / suggestions
Re: HOTKEY - problems / suggestions #61
Re: HOTKEY - problems / suggestions #62
Posted 25 September 2014 - 22:47
Also, I am already using QuickButton to assign LONG GREEN to BitrateViewer and HOTKEY does not see that. Is this normal?
I don't know... possible MQB is overruled.... I have long green as bitrateviewer in Hotkey...
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: HOTKEY - problems / suggestions #63
Posted 25 September 2014 - 23:07
Here this
--- Hotkey.py.orig
+++ Hotkey.py
@@ -362,10 +362,14 @@
exec "self." + selected[1] + "()"
elif selected[0] == "Module":
try:
- exec "from " + selected[1] + " import *"
+ exec "import " + selected[1]
+ for p in dir(selected[1]):
+ exec "from " + selected[1] + " import " + p
exec "self.session.open(" + ",".join(selected[2:]) + ")"
except:
print "[Hotkey] error during executing module %s, screen %s" % (selected[1], selected[2])
elif selected[0] == "Setup":
- from Screens.Setup import *
+ import Screens.Setup
+ for p in dir(Screens.Setup):
+ exec "from Screens.Setup import " + p
exec "self.session.open(Setup, \"" + selected[1] + "\")"
Doesn't work...???
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: HOTKEY - problems / suggestions #64
Re: HOTKEY - problems / suggestions #65
Re: HOTKEY - problems / suggestions #66
Posted 26 September 2014 - 06:05
Here this ... Doesn't work...???
It's possible, i didn't test it yet, only test that syntax warning goes away.
Did http://sourceforge.n...766b64d0e4bc6d/ worked?
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916
Re: HOTKEY - problems / suggestions #67
Re: HOTKEY - problems / suggestions #68
Posted 26 September 2014 - 06:37
for et9x00
Mark=KEY_BOOKMARKS
Vkey= KEY_VIDEO
+
not solved:
add action(historyBack/historyNext) for key Left/Right -->run video-->rewind for key Left/Right do not work
The kays should be probably added... The not solved part I do not understand what you mean.... In addition it is not such a good idea to alter left/right buttons....Then indeed in movieplayer you did overule them by yourself...
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: HOTKEY - problems / suggestions #69
Re: HOTKEY - problems / suggestions #70
Posted 26 September 2014 - 08:33
Also, I am already using QuickButton to assign LONG GREEN to BitrateViewer and HOTKEY does not see that. Is this normal?I don't know... possible MQB is overruled.... I have long green as bitrateviewer in Hotkey...
No, no, I'm not using MQB, it is QuickButton. And LONG GREEN still works as bitrateviewer as assigned by Quickbutton.
It is HOTKEY that does not "see" that in the sense that it does not show anything assigned to LONG GREEN.
ET9000, OpenPLi 4.0, 13E, 19E
HD51, OpenPLi 6.2, 75E - 30W
Re: HOTKEY - problems / suggestions #71
Posted 26 September 2014 - 08:42
Buttons f1 etc do not exists on vu... But they exist on et10k...
To avoid this we need to find a way to enable/disable specific buttons by remote control selected...
Edited by littlesat, 26 September 2014 - 08:47.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: HOTKEY - problems / suggestions #72
Posted 26 September 2014 - 10:18
If that is the case, than quickbutton overrules hotkey... Nothing todo about this... I'm afraid quickbutton uses a higher priority and does not perform a return 0 to allow lowe priority actions...
QuickButton is very limited in its functionality. It can only assign 4 keys: all LONG coloured buttons.
I think I will now deselect LONG GREEN from QuickButton and stop using this plugin.
Instead I will select LONG GREEN for BitrateViewer in HOTKEY and that's it.
ET9000, OpenPLi 4.0, 13E, 19E
HD51, OpenPLi 6.2, 75E - 30W
Re: HOTKEY - problems / suggestions #73
Re: HOTKEY - problems / suggestions #74
Posted 26 September 2014 - 10:51
But when it is not workink here I know you're able to fix this
Personally I do not see the advantage of the history zap selector plugin...
Edited by littlesat, 26 September 2014 - 10:52.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: HOTKEY - problems / suggestions #75
Posted 26 September 2014 - 11:12
class hotkeyActionMap(ActionMap): + from Components.ServiceEventTracker import InfoBarCount def action(self, contexts, action): + if InfoBarCount != 1: return 1 if (action in tuple(x[1] for x in hotkeys) and self.actions.has_key(action)): res = self.actions[action](action) if res is not None: return res return 1 else: return ActionMap.action(self, contexts, action)
This is just a guess ...
GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K
Re: HOTKEY - problems / suggestions #76
Posted 26 September 2014 - 11:17
Then it is better to add a sanity check in history zap and return 0 or so to allow to find a better action.
But wierd... i check for the function being available before executing it....?
Edited by littlesat, 26 September 2014 - 11:20.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: HOTKEY - problems / suggestions #77
Re: HOTKEY - problems / suggestions #78
Posted 26 September 2014 - 16:28
Maybe I again miss something, but why is necessary this evil imoprt *?
If there is a "Module" we know what we start, why not import just it?
If there is a "Setup", then we call Setup, why not import just Setup?
I think the code should be:
elif selected[0] == "Module": try: screen = ",".join(selected[2:]) exec "from " + selected[1] + " import " + screen exec "self.session.open(" + screen + ")" except: print "[Hotkey] error during executing module %s, screen %s" % (selected[1], selected[2]) elif selected[0] == "Setup": from Screens.Setup import Setup exec "self.session.open(Setup, \"" + selected[1] + "\")"
Re: HOTKEY - problems / suggestions #79
Posted 26 September 2014 - 17:52
@littlesat
with this commit: http://sourceforge.n...c61393faacf7c9/
'Portal' key has been (accidentally?) removed from the Hotkey...
Re: HOTKEY - problems / suggestions #80
30 user(s) are reading this topic
0 members, 30 guests, 0 anonymous users