Jump to content


Photo

HOTKEY - problems / suggestions


  • Please log in to reply
579 replies to this topic

Re: HOTKEY - problems / suggestions #121 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 4 October 2014 - 16:17

I'm glad Littlesat created this 'Hotkey' functionality. It really added value to PLi.

 

One suggestion though: could all functionality that is assigned show in the 'choosen' list? As it is now only changed functionality shows there.

e.g.: by default long-red is assigned to HbbTV. But it only shows in the list, when Hotkey has been used to connect the two.



Re: HOTKEY - problems / suggestions #122 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 4 October 2014 - 16:41

Sorry I do not understand what you meant... short red is standard HbbTV...???

 

It is easy to add functionality in Hotkey.py... so you can alwayse come up with a suggestions...

 

Functionality could be made default... For now it is only overruling the default... Note when functions are made default in the Hotkey.py, keymap additions in the normal infoBar at least could be removed... This is still something I'm considering. But I think I will leave the standard as it is and not add it in the Hotkey list... Nothing in the hotkey list means standard function... ;)

 

Note that the "reduced" button are those that basically do not have functionality... I would recommend to only change these buttons.


Edited by littlesat, 4 October 2014 - 16:44.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: HOTKEY - problems / suggestions #123 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 4 October 2014 - 17:29

Hotkey lists all buttons; many of them have a functionality assigned by default.

It would be nice if the actual assignment would show in Hotkey, whether or not it is Hotkey that did this assignment. This way the overview would be much better.


Edited by SatKiekerd, 4 October 2014 - 17:30.


Re: HOTKEY - problems / suggestions #124 WanWizard

  • PLi® Core member
  • 70,220 posts

+1,798
Excellent

Posted 4 October 2014 - 17:36

I wonder if it is that easy. "default" depends on context, so the hotkey list shown must also depend on context for that to work. And that might create more confusion than it solves...


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: HOTKEY - problems / suggestions #125 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 4 October 2014 - 17:40

MQB does a good job in that area: it reads all actual functionality. So I'm pretty sure Littlesat can do the same....

And what confusion could a complete overview give us?

 

Oh, maybe also a 'back to default' option?



Re: HOTKEY - problems / suggestions #126 WanWizard

  • PLi® Core member
  • 70,220 posts

+1,798
Excellent

Posted 4 October 2014 - 17:45

Well, for example, in the service selector short red is not HbbTV, it's "Show all channels list". Which is what I mean with "context'.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: HOTKEY - problems / suggestions #127 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 4 October 2014 - 18:04

Hotkey is only active in the main InfoBar and MoviePlayer Infobar...

I just committed something related to the EPG functionality and buttons. It removed a lot of code in InfoBarGenerics. Here I think it makes sense as these keys were already somehow configurable...


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: HOTKEY - problems / suggestions #128 Robinson

  • Senior Member
  • 2,621 posts

+30
Good

Posted 4 October 2014 - 18:05

WanWizard, yes, but my understanding is that HOTKEY is mainly (only?) for the main screen, namely when watching satellite. It is not for context usage. Or am I wrong here?


Edited by Robinson, 4 October 2014 - 18:06.

ET9000, OpenPLi 4.0, 13E, 19E

HD51, OpenPLi 6.2, 75E - 30W


Re: HOTKEY - problems / suggestions #129 WanWizard

  • PLi® Core member
  • 70,220 posts

+1,798
Excellent

Posted 4 October 2014 - 19:02

Ok.

 

Ideally, you would have a single system to handle all RC interaction, so I hope this will evolve to be exactly that.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: HOTKEY - problems / suggestions #130 Taapat

  • PLi® Core member
  • 2,345 posts

+121
Excellent

Posted 4 October 2014 - 21:23

@ littlesat in this commit: http://sourceforge.n...ad604a34c8a4cd/

in class HotkeySetupSelect in def keyOk you changed to:

self.selected.append(currentSelected[:2])

but forgot that whit this also need be changed to:

else:
  if currentSelected[:2] in self.selected:
    self.selected.remove(currentSelected[:2])

Currently, without this, it is impossible to remove added functions.


Edited by Taapat, 4 October 2014 - 21:26.


Re: HOTKEY - problems / suggestions #131 Taapat

  • PLi® Core member
  • 2,345 posts

+121
Excellent

Posted 4 October 2014 - 21:40

And just an idea for the future.

Maybe buttons for hotkeys can be taken from rc_models? I do not know how correct is data in the xml files, but if they are correct, then for each receiver could offer only those buttons, that are in their remote control.



Re: HOTKEY - problems / suggestions #132 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 4 October 2014 - 22:37

Shoot indeed... :(... I did test delete from the choosen list so I did not notify....

For the available buttens per remote control I do not have a good solution yet...

Edited by littlesat, 4 October 2014 - 22:40.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: HOTKEY - problems / suggestions #133 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 October 2014 - 05:25

For the available buttens per remote control I do not have a good solution yet...

And especially for boxes that support multiple RC's (Xtrend does) this might even be more difficult.

 

@ Littlesat: Would it be possible to add several buttons, like Up/Down/Left/Right-LONG and Power-Short/Long?

The latter would omit the need to have the default E2 settings for action on Power-button.



Re: HOTKEY - problems / suggestions #134 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 October 2014 - 06:00

A request: would it be possible to display the categories in a different lay-out? As it is now they are not distinguishable from the functions.

 

 

A bug: when adding 'HbbTV Applications' the function changes to 'Browser Start/Stop' at the moment the functionality is being saved.

Tested on Solo2 on yesterday's PLi (there is no build today) and with the latest changes in Hotkey, InfoBar & InfoBarGenerics taken from the repos).



Re: HOTKEY - problems / suggestions #135 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 October 2014 - 06:09

A second bug: assigning 'Grafische Multi EPG' to the button 'Epg/Guide' doesn't work. The assignment is there, but on pushing the guide-button still 'EventView' (which is the default value for that button) pops up.

 

Also tested on Solo2 on yesterday's PLi (there is no build today) and with the latest changes in Hotkey, InfoBar & InfoBarGenerics taken from the repos).



Re: HOTKEY - problems / suggestions #136 santa

  • Member
  • 20 posts

+1
Neutral

Posted 5 October 2014 - 07:41

I think it's much easier if you press the key you want to change, instead of these long list.
Default keys like cursors, colored and exit must be the only keys in list, cause you need them to change.

Keys that you have change should be in this list to, then you know which key is set and which not.

Edited by santa, 5 October 2014 - 07:42.


Re: HOTKEY - problems / suggestions #137 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 5 October 2014 - 08:40

Up down left right long will not be added.... As when doing this you must change the short to the release of the button and that does reduce response time and that irritates... I think this is a bad work-a-round.
Especially with zap functions... I suggest there are enough buttons to assign...
Power long short could be considered... As this is and was always a short long button... Then also a config could be removed..
I do not see the hbbtv bug...?
Press the key could also be considered when you are in the long list... Good idea... It is only a bit difficult for red/green...

I get gmepg... So i cannot verify this issue also...?

What functions will be pushed in which catagorie is very easy,,, it is the third parameter in the function definitions.. Come with your logical suggestion...

Edited by littlesat, 5 October 2014 - 08:50.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: HOTKEY - problems / suggestions #138 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 October 2014 - 09:13

I do not see the hbbtv bug...?

Well, I confirm it's also present on the DUO2.

Did you check what happens on saving the assignment to HbbTV applications?

 

And what about the G-EPG bug I reported? Maybe you tried on a box that has both Guide & Info buttons?


Edited by SatKiekerd, 5 October 2014 - 09:16.


Re: HOTKEY - problems / suggestions #139 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 5 October 2014 - 09:32

I indeed tried on a box that has both buttons... and default on the other button current event is and was the default..

 

From hotkey you can the (opera) browser...not HbbTV itself yet... (possibly for that we need to add a new infoBar funtion)


Edited by littlesat, 5 October 2014 - 09:33.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: HOTKEY - problems / suggestions #140 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 October 2014 - 10:22

There are 3 options: Browser Start/Stop, HbbTV Applications & Opera Web Browser.

They all lead to the setting Browser start/stop and that's indeed what's being assigned effectively. So HbbTV cannot (effectively) be assigned and hence must be left to the default (short-red).




19 user(s) are reading this topic

0 members, 19 guests, 0 anonymous users