Jump to content


Photo

HOTKEY - problems / suggestions


  • Please log in to reply
579 replies to this topic

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

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 October 2014 - 12:12

@ Littlesat: The changes you committed to Hotkey this morning lead to an E2-crash:

Attached File  enigma2_crash_1412507276.log   16.99KB   6 downloads

 

This is on pushing 'Guide' after assigning 'G-EPG' to guide via Hotkey.

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 #142 Bay

  • Senior Member
  • 87 posts

+1
Neutral

Posted 5 October 2014 - 12:43

I will "Show InfobarTunerState ",but it is allways "InfobarTunerState" :wub: Iwill "Cool Info Guide",but it is allways Cool Channel Guide" :wub:

It`s always still the same.Box ET9200.



Re: HOTKEY - problems / suggestions #143 Dimitrij

  • PLi® Core member
  • 10,263 posts

+347
Excellent

Posted 5 October 2014 - 13:11

Littlesat

Please revert this commit:

http://sourceforge.n...6703768262d748/

Long EPG - list of plugins event info.

It is a standard enigma2.


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: HOTKEY - problems / suggestions #144 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 5 October 2014 - 13:13

I can confirm GSOD with EPG button ...  about modal

 

Edit: And It seems, does work nothing from category "Setup" 

 

EDIT1: Blue long - Ppanels - GSOD ... about modal

 

EDIT2: problems about modals window

 

Todays's changes


Edited by ims, 5 October 2014 - 14:40.

Kdo nic nedělá, nic nezkazí!

Re: HOTKEY - problems / suggestions #145 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 5 October 2014 - 16:22

REM line self.session.open(dummyScreen) solved all for me.


Edited by ims, 5 October 2014 - 16:22.

Kdo nic nedělá, nic nezkazí!

Re: HOTKEY - problems / suggestions #146 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 5 October 2014 - 16:28

Then it seems i need to find a different solution for long/short stuff....
@dima73 I will not revert as this is all replaced in Hotkey...

Edited by littlesat, 5 October 2014 - 16:29.

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


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

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 October 2014 - 17:29

G-EPG OSD fixed with the 17.48 update. But still no G-EPG on 'Guide'-button (but the default EventView).



Re: HOTKEY - problems / suggestions #148 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 5 October 2014 - 17:32

I have GMEPG on Guide button here??????? On Info button I have Event View....????

I think Info button should be Event View and GMEPG on Guide...


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


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

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 October 2014 - 17:35

As I said: you are testing on a box having both those buttons. VU's only have a guide-button (defaulting to EventView, whatever the Hotkey setting).


Edited by SatKiekerd, 5 October 2014 - 17:39.


Re: HOTKEY - problems / suggestions #150 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 5 October 2014 - 18:35

I think, VU has problem with text versus sended KEY_CODE. On VU sending EPG button KEY_INFO, and not KEY_EPG.

 

Usually it was solved in keymap.xml, that for same action was used KEY_INFO and KEY_EPG. But this is better for users with INFO and EPG on RC now.


Edited by ims, 5 October 2014 - 18:36.

Kdo nic nedělá, nic nezkazí!

Re: HOTKEY - problems / suggestions #151 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 5 October 2014 - 18:55

IMS, can this be adapted, so the good code is send???? It seems more the fact that the incorrect key info is send somehow... :(

PLi does not like code as if vu then....... basically it was also not default previously....

 

I wanted to try to remove more from infobargenerics and make stuff default via Hotkey... (e.g. audioselection, subtitle, all color buttons.... but not the cursor keys...)


Edited by littlesat, 5 October 2014 - 18:58.

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


Re: HOTKEY - problems / suggestions #152 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 5 October 2014 - 19:21

I think - progres was: DMM has INFO button and sending KEY_INFO => VU has INFO only too, but designers in VU wrote on RC button text "EPG".

RC sending own code and ( i think) - driver - translate it for enigma's codes.

 

May be - make test, if box's driver has KEY_EPG... but it is not possible, when enigma is running, i think.


Edited by ims, 5 October 2014 - 19:21.

Kdo nic nedělá, nic nezkazí!

Re: HOTKEY - problems / suggestions #153 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 5 October 2014 - 19:22

But this is not a "new" issue... I mean not an issue induced by Hotkey....


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


Re: HOTKEY - problems / suggestions #154 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 5 October 2014 - 19:39

yes and no ... :)   you remove part, where was aranged type of EPG for INFO and EPG buttons, and divide INFO and EPG to standallone way.

I think, there coud be text for EPG button in Hotkey: "Use INFO, if on RC exist EPG button only!" :)


Kdo nic nedělá, nic nezkazí!

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

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 October 2014 - 20:53

But whatever the default is: HotKey should be able to change it?



Re: HOTKEY - problems / suggestions #156 blzr

  • PLi® Core member
  • 2,270 posts

+118
Excellent

Posted 5 October 2014 - 21:21

and it is able, as far as I understood (see @ims explanations above #152),
in vu, the 'epg/guide' button is the 'info' button actually, so you need to assign function to 'Info' in Hotkey setup


True sarcasm doesn't need green font...

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

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 5 October 2014 - 21:25

Ah, indeed, I missed that; works that way!



Re: HOTKEY - problems / suggestions #158 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 5 October 2014 - 22:00

... and after littlesat's last commit will not be problem with it more (http://sourceforge.n...b65e7180977c6/)

 

 

Only note for littlesat - may be:

 

- remove Toggle .Extra Keys => will works for green too (now must be pressed Green 2x for focus on it)

- remove Red and leave Hotkey with EXIT button


Edited by ims, 5 October 2014 - 22:16.

Kdo nic nedělá, nic nezkazí!

Re: HOTKEY - problems / suggestions #159 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 5 October 2014 - 22:11

I'm also considering to remove toggle extra keys... And fed key could also be removed there....

Finally the begin was easy.... Finetuning is a different job....

Edited by littlesat, 5 October 2014 - 22:11.

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


Re: HOTKEY - problems / suggestions #160 ims

  • PLi® Core member
  • 13,764 posts

+214
Excellent

Posted 5 October 2014 - 22:17

Only cosmetic:

1) PVR in Hotkey is KEY_RECORDS button => would not be better using text REC for it there in Hotkey ? On most boxes it is red point only or text REC

2) List/Fav is KEY_VIDEO => text "List/Fav/PVR"  ?


Edited by ims, 5 October 2014 - 22:17.

Kdo nic nedělá, nic nezkazí!


11 user(s) are reading this topic

0 members, 11 guests, 0 anonymous users