After downloading from git the new Hotkey.py, 'Restart', 'Restart enigma', 'Standby' and 'Deep standby' works perfectly here
HOTKEY - problems / suggestions
Re: HOTKEY - problems / suggestions #21
Re: HOTKEY - problems / suggestions #22
Re: HOTKEY - problems / suggestions #23
Re: HOTKEY - problems / suggestions #25
Re: HOTKEY - problems / suggestions #26
Posted 22 September 2014 - 20:21
make brake release long....?
What did you meant with sleeptimer???? That is in there already I suppose....
hotkeyFunctions.append((_("Sleeptimer"), "Module/Screens.SleepTimerEdit/SleepTimerEdit"))
Edited by littlesat, 22 September 2014 - 20:27.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: HOTKEY - problems / suggestions #27
Re: HOTKEY - problems / suggestions #28
Posted 23 September 2014 - 05:29
make brake release long....?
What did you meant with sleeptimer???? That is in there already I suppose....
hotkeyFunctions.append((_("Sleeptimer"), "Module/Screens.SleepTimerEdit/SleepTimerEdit"))
hotkeyFunctions.append((_("Sleeptimer"), "Module/Screens.SleepTimerEdit/SleepTimerEdit"))
hotkeyFunctions.append((_("Sleeptimer edit"), "Module/Screens.SleepTimerEdit/SleepTimerEdit"))
GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K
Re: HOTKEY - problems / suggestions #29
Posted 23 September 2014 - 14:09
for
hotkeyFunctions.append((_("swapPiP"), "Infobar/swapPiP")) hotkeyFunctions.append((_("movePiP"), "Infobar/movePiP"))
additional check:
def swapPiP(self): + if not self.pipShown(): + return swapservice = self.session.nav.getCurrentlyPlayingServiceOrGroup() pipref = self.session.pip.getCurrentService() if swapservice and pipref and pipref.toString() != swapservice.toString(): currentServicePath = self.servicelist.getCurrentServicePath() self.servicelist.setCurrentServicePath(self.session.pip.servicePath, doZap=False) self.session.pip.playService(swapservice) self.session.nav.playService(pipref, checkParentalControl=False, adjust=False) self.session.pip.servicePath = currentServicePath if self.servicelist.dopipzap: # This unfortunately won't work with subservices self.servicelist.setCurrentSelection(self.session.pip.getCurrentService()) def movePiP(self): + if not self.pipShown(): + return self.session.open(PiPSetup, pip = self.session.pip) def pipDoHandle0Action(self):
GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K
Re: HOTKEY - problems / suggestions #30
Re: HOTKEY - problems / suggestions #31
Re: HOTKEY - problems / suggestions #32
Re: HOTKEY - problems / suggestions #33
Re: HOTKEY - problems / suggestions #34
Posted 24 September 2014 - 10:18
I have two suggestions to make the hotkey setup function a little more user-friendly:
- In the first setup screen the keys that can be assigned are shown. It would be nice to see any assigned functions in a second column on that screen.
- In the screen showing the functions that can be assigned, the order in which the functions are presented could be somewhat more logical
For the rest: I have now dropped MultiQuickButton. I can do all the re-assignments I used to do with MQB in the new HotKey functionality! Good work!
Re: HOTKEY - problems / suggestions #35
Posted 24 September 2014 - 11:36
This is all fine and well,but we need an option to remove these choices too incase we change our minds or make a mistake.
As it is now nothing can be done to revert the settings,even trying to use MQB to revert the changes doesnt work.Once a key has been assigned to something using the Hotkey feature,MQB will then no longer work on that key afterwards.
So at the moment you are stuck with what you choose first time.
Any news on the sanity check for pluginsort/menusort ?
Ian.
Edited by ian1095, 24 September 2014 - 11:40.
Re: HOTKEY - problems / suggestions #36
Posted 24 September 2014 - 11:56
This is all fine and well,but we need an option to remove these choices too incase we change our minds or make a mistake.
As it is now nothing can be done to revert the settings,even trying to use MQB to revert the changes doesnt work.Once a key has been assigned to something using the Hotkey feature,MQB will then no longer work on that key afterwards.
So at the moment you are stuck with what you choose first time.
Any news on the sanity check for pluginsort/menusort ?
Ian.
Press bouquet up and then just ok
ET10000+ Openpli 6.1,1m schotel 4x duo-lnb op vaste opstelling.
Momolights teensy 2.0 met 50 leds op een string ,150 channels
DM8000 Openpli 6.1 Release
Re: HOTKEY - problems / suggestions #37
Re: HOTKEY - problems / suggestions #38
Posted 24 September 2014 - 12:06
This is all fine and well,but we need an option to remove these choices too incase we change our minds or make a mistake.
As it is now nothing can be done to revert the settings,even trying to use MQB to revert the changes doesnt work.Once a key has been assigned to something using the Hotkey feature,MQB will then no longer work on that key afterwards.
So at the moment you are stuck with what you choose first time.
Any news on the sanity check for pluginsort/menusort ?
Ian.
Press bouquet up and then just ok
Ah Thank You.
I didnt know that lol.
Works perfectly.
Ian.
Re: HOTKEY - problems / suggestions #39
Posted 24 September 2014 - 14:13
In addition it is a bit strange... Plugin does not have a value None... Plugin name should have a name... But somehow these plugins do change the folder or so from the plugin lists
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: HOTKEY - problems / suggestions #40
Posted 24 September 2014 - 14:30
Edited by littlesat, 24 September 2014 - 14:34.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
3 user(s) are reading this topic
0 members, 3 guests, 0 anonymous users