579 replies to this topic

[Taapat]

Why do you need such a structure where there is only a long translation?

("F1" + " " + _("long"), "f1_long", ""),

And why not simply?

("F1 " + _("long"), "f1_long", ""),

[40H3X]

...is it an idea to not let the user choose the key, as there is much difference in key codes between different boxes. So IMHO would it be an idea to select a hotkey "only" by pressing it, instead of letting users choose it.

[Taapat]

Try to press the required button. You jump to required button in the list. 
I think that would be good if the same could be jumping on the selected function. In collapse list sometimes is difficult to find the necessary, to disable. But of course I'm not doing it every day, so I can also look longer and more carefully.

[littlesat]

Because with with one we need to translate "F1 " and with the other "F1"

[Taapat]

But if the idea of ims is not translate the F1 but only long?
Although after the last changes translates also F1.

Edited by Taapat, 12 November 2014 - 01:08.

[littlesat]

Good suggestion... It was also in line with the rest.... Let me thing about this...

[greatred]

...is it an idea to not let the user choose the key, as there is much difference in key codes between different boxes. So IMHO would it be an idea to select a hotkey "only" by pressing it, instead of letting users choose it.

 

Speaking of pressing the key to select it in HotKey:

 

I`m not able to jump to PAUSE, it will always go to Play 

[ims]

it seems, your box using for "Pause" code "Play"

[Rob van der Does]

This is brand-dependant; some boxes have dedicated play & pause buttons, some have one combined Play/Pause button.

[ims]

 

Why do you need such a structure where there is only a long translation?

("F1" + " " + _("long"), "f1_long", ""),

And why not simply?

("F1 " + _("long"), "f1_long", ""),

Always is better define strings without space on begin and end. Then better would be use:

 ("%s %s" % ("F1", _("long")), "f1_long", ""),

but in all case, line

self.list.append(ChoiceEntryComponent('',(_(x[0]), x[1])))

translating then in _(x[0]) all strings again (unwanted too) - it is next gettext on all strings

Edited by ims, 12 November 2014 - 11:14.

[greatred]

it seems, your box using for "Pause" code "Play"

 

No idea what code my VU+ Uno is using for PAUSE

 

This is brand-dependant; some boxes have dedicated play & pause buttons, some have one combined Play/Pause button.

 

VU+ Uno Remote does have two separate buttons for PAUSE and PLAY.

 

 vu_normal.png   19.97KB   9 downloads

Edited by greatred, 12 November 2014 - 09:54.

[Taapat]

Yes, I can confirm that removing the _ in _(x [0]) is translated only what is necessary, not all.

[ims]

 

it seems, your box using for "Pause" code "Play"

 

No idea what code my VU+ Uno is using for PAUSE

 

This is brand-dependant; some boxes have dedicated play & pause buttons, some have one combined Play/Pause button.

 

VU+ Uno Remote does have two separate buttons for PAUSE and PLAY.

 

vu_normal.png

 

And there in enigma, this buttons works well ?

[Rob van der Does]

VU+ Uno Remote does have two separate buttons for PAUSE and PLAY.

Yes, but given the fact that the latest VU RC's have a combined button, it's very well possible that both are mapped to the combined Play/Pause-command in PLi.
And the reaction in Hotkey seems to confirm that.

[ims]

I think, this RC is possible configure for 2 groups of VU boxes. May be it is wrong configured ?

 

@SatKiekerd ... again some wrong in PLi ?

[greatred]

How is this solved with MQB ? I`m able to assign actions to PLAY, keeping PAUSE functionality untouched.

I compared the keymap.xml with MQB installed and without, cannot see a single difference.

[ims]

How it works on clear E2 ( without MQB) ? Works this buttons separately - f.eg. || (pause) activating Timeshift and Play run playback of timeshist.

 

How you can know codes for your buttons:

 

install in telnet evtest:  opkg install evtest

then stop enigma with:  init 4

 

then run: evtest    and select number for your RC

then press any buttons and you will see, which number code is used and which KEY_CODE.

 

back to work run: init3

[greatred]

Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "dreambox advanced remote control (native)"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 2 (KEY_1)
    Event code 3 (KEY_2)
    Event code 4 (KEY_3)
    Event code 5 (KEY_4)
    Event code 6 (KEY_5)
    Event code 7 (KEY_6)
    Event code 8 (KEY_7)
    Event code 9 (KEY_8)
    Event code 10 (KEY_9)
    Event code 11 (KEY_0)
    Event code 102 (KEY_HOME)
    Event code 103 (KEY_UP)
    Event code 104 (KEY_PAGEUP)
    Event code 105 (KEY_LEFT)
    Event code 106 (KEY_RIGHT)
    Event code 107 (KEY_END)
    Event code 108 (KEY_DOWN)
    Event code 109 (KEY_PAGEDOWN)
    Event code 113 (KEY_MUTE)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 116 (KEY_POWER)
    Event code 128 (KEY_STOP)
    Event code 138 (KEY_HELP)
    Event code 139 (KEY_MENU)
    Event code 163 (KEY_NEXTSONG)
    Event code 164 (KEY_PLAYPAUSE)
    Event code 165 (KEY_PREVIOUSSONG)
    Event code 167 (KEY_RECORD)
    Event code 174 (KEY_EXIT)
    Event code 207 (KEY_PLAY)
    Event code 272 (BTN_LEFT)
    Event code 273 (BTN_RIGHT)
    Event code 352 (KEY_OK)
    Event code 358 (KEY_INFO)
    Event code 370 (KEY_SUBTITLE)
    Event code 377 (KEY_TV)
    Event code 385 (KEY_RADIO)
    Event code 388 (KEY_TEXT)
    Event code 392 (KEY_AUDIO)
    Event code 393 (KEY_VIDEO)
    Event code 398 (KEY_RED)
    Event code 399 (KEY_GREEN)
    Event code 400 (KEY_YELLOW)
    Event code 401 (KEY_BLUE)
    Event code 402 (KEY_CHANNELUP)
    Event code 403 (KEY_CHANNELDOWN)
    Event code 407 (KEY_NEXT)
    Event code 412 (KEY_PREVIOUS)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max     1280
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      720
Properties:
Testing ... (interrupt to exit)
Event: time 1415783769.224674, type 1 (EV_KEY), code 165 (KEY_PREVIOUSSONG), value 1
Event: time 1415783769.224680, -------------- EV_SYN ------------
Event: time 1415783769.562471, type 1 (EV_KEY), code 165 (KEY_PREVIOUSSONG), value 0
Event: time 1415783769.562476, -------------- EV_SYN ------------
Event: time 1415783771.440214, type 1 (EV_KEY), code 207 (KEY_PLAY), value 1
Event: time 1415783771.440220, -------------- EV_SYN ------------
Event: time 1415783771.670470, type 1 (EV_KEY), code 207 (KEY_PLAY), value 0
Event: time 1415783771.670474, -------------- EV_SYN ------------
Event: time 1415783774.304364, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 1
Event: time 1415783774.304370, -------------- EV_SYN ------------
Event: time 1415783774.535475, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 0
Event: time 1415783774.535479, -------------- EV_SYN ------------
Event: time 1415783775.604697, type 1 (EV_KEY), code 163 (KEY_NEXTSONG), value 1
Event: time 1415783775.604704, -------------- EV_SYN ------------
Event: time 1415783775.835471, type 1 (EV_KEY), code 163 (KEY_NEXTSONG), value 0
Event: time 1415783775.835476, -------------- EV_SYN ------------
Event: time 1415783781.164404, type 1 (EV_KEY), code 128 (KEY_STOP), value 1
Event: time 1415783781.164410, -------------- EV_SYN ------------
Event: time 1415783781.288470, type 1 (EV_KEY), code 128 (KEY_STOP), value 0
Event: time 1415783781.288474, -------------- EV_SYN ------------

Thanks for the tip with evtest

[ims]

Then you can see, that you have not KEY_PLAY (207) and KEY_PAUSE (119), but KEY_PLAY (207) and KEY_PLAYPAUSE (164).

 

As I saw, there in HOTKEY is used KEY_PLAY and KEY_PLAYPAUSE as same function "play". Ask to littlesat, to divide it into 2 standalone:

 

KEY_PLAY as "play"

KEY_PLAYPAUSE as "playpause"

[greatred]

Then you can see, that you have not KEY_PLAY (207) and KEY_PAUSE (119), but KEY_PLAY (207) and KEY_PLAYPAUSE (164).

 

Yeah I noticed that PLAYPAUSE is there instead of PAUSE.

 

 

As I saw, there in HOTKEY is used KEY_PLAY and KEY_PLAYPAUSE as same function "play". Ask to littlesat, to divide it into 2 standalone:

 

KEY_PLAY as "play"

KEY_PLAYPAUSE as "playpause"

 

If such a change is cosmetic and is not interfering with other remotes/boxes then I opt for adjusting this.

 

@littlesat could you please consider this ?