579 replies to this topic

[Rob van der Does]

Done, and same result as in Hotkey

Dedicated Play-button:
Event: time 1415869269.110626, type 1 (EV_KEY), code 207 (KEY_PLAY), value 1

Dedicated Pause-button:
Event: time 1415869274.160284, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 1

Combined PlayPause button:
Event: time 1415869416.929118, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), value 2

This is on UNO on up-to-date PLi

[ims]

I am little lost now ... where is problem ?

 

rc's button:

PLAY ... (207)

PLAYPAUSE ... (164)  code KEY_PLAYPAUSE

PAUSE ... (164) code KEY_PLAYPAUSE

 

hotkey using what goes from rc and driver=>Playpause and pause are same in your case.

Edited by ims, 13 November 2014 - 10:20.

[Rob van der Does]

OK, so it's one of VU's driver issues then? Using a wrong command (key), just like they do for EPG/Info?

[ims]

I do not know, why there are 2 buttons with same code. It can be driver, but it can be RC too (2 buttons sending same code)

[ims]

But why there is: value 2 ???

 

Standardly is value = 1 for pressed button, value = 0 for released button.

value = 2 ?

[Rob van der Does]

I do not know, why there are 2 buttons with same code. It can be driver, but it can be RC too (2 buttons sending same code)

As I said: that's on different RC's.
The old VU RC has the two dedicated Play & Pause buttons (the latter sending key 164 as we found out), while the new VU RC only has the single PlayPause button.

Any idea why VU uses key 164 for the dedicated pause-button? Would '"KEY_PAUSE": 119' not be more appropriate?

I tried to compare with the Xtrend9200, but there I can't get evtest to run properly.

Edited by SatKiekerd, 13 November 2014 - 11:28.

[Rob van der Does]

But why there is: value 2 ???
 
Standardly is value = 1 for pressed button, value = 0 for released button.
value = 2 ?

I have no idea.

[ims]

I saw on my VU Ultimo - original RC (with keyboard on back side) :

 

Play:  KEY_PLAY

Pause: KEY_PLAYPAUSE

[Rob van der Does]

Yep, also the same.
So it beats me why VU uses playpause instead of pause.

[Erik Slagter]

Hotkey - added Language selection into Setup

Applied by Littlesat.

[Erik Slagter]

Here is patch for it:

Applied by Littlesat.

[findex]

Why is the "OK" button not available? Is there a special reason?

I would like to use it to call CoolTV Multi Guide.

Is there a chance that you add it or how could I solve this in a different way?

 

Many thanks for this great plugin and in general for the whole image!!!

Edited by findex, 16 November 2014 - 14:38.

[littlesat]

I suggest it is not smart to replace the OK button.... but it can be added for people who want to do crazy things...

[littlesat]

OK button added...

 

http://sourceforge.n...aa8543f5901a34/

[ims]

may be only as "long" ?

[littlesat]

Nope... when we make it short/long then the normal response time for that button will delay with approx 200 msec because short becomes release button in that case... And that is something we do not want on such general key

Edited by littlesat, 16 November 2014 - 14:49.

[findex]

Many thanks for your quick response.

 

Not so sure why you think this is a crazy request. I use it like this since years with MultiQuickButton.

I assume the Hotkey mapping is only active during watching TV and not during other menus or plugins or movie player are active.

Am I wrong?

 

 

[littlesat]

Where do you put toggle infobar?

[findex]

On "Exit" as by default.

[ims]

funny ... and "1" si on "9" and "3" on "7" ?