Buggy behavior arrowing through Now Playing menu, menu position jumps out of place

[mvallevand]

I agree it is weird but they primarily designed for channel up and down and I wanted up to be channel up etc.

I think I am using 500ms for long which is pretty standard.

Martin

[sub]

At least it's all becoming more clear now.

[mmortal03]

At least it's all becoming more clear now.

I agree with Martin that a long-press-up should go up a channel, and a long-press-down should go down a channel, but it's not at all intuitive for a long-press-up while inside a list box to go down a page, and a long-press-down while inside a list box to go up a page.

Are the commands/codes that are being sent when the list box *isn't* visible not separable from the commands being sent when the list box *is* visible? Is it hard coded in the Roku to move one way in one context, but the other way in a different context?

Regarding the 500ms for long press, Martin may be right that that's standard -- it may be some sort of latency on my server yet again. I hope to find a solution to optimize this, though. I don't see how sending remote or keyboard commands could be process-intensive.

[sub]

In case it's not clear, it's not NextPVR doing this long press behaviour. It doesn't know anything about long vs short presses. This is something happening on the Roku client side. The client also doesn't know the context of what is on the screen, so has to handle things in a fairly generic way.

It may be just a case of Martin needing to tweak this 500ms to be a bit longer so you're getting more consistent behaviour. (or if he gets button-down/button-up notifications, there might be other options to get more accurate information about whether it was a long/short press)

[mvallevand]

The issue is because NextPVR (incluiding PC client) reverses what channel +/- do by name. Channel plus goes down a channel and Channel minus goes up. Swap them in KeyMapping.xml where you can change the + to - and - to +.

Code:

<Key code="Add" command="Channel+"/>
      <Key code="Subtract" command="Channel-"/>
      <Key code="Next" command="Channel-"/>
      <Key code="PageUp" command="Channel+"/>

For the code yes, it is state specific

Code:

.
else if msg = keyCode["button_down_released"]
    if m.state = "live tv"
        if longPress
            key = "33"
        else
            key = "40"
        end if
    else
        key = "40"
    end if

Martin

[mmortal03]

Ah, I see. This is what I see for the defaults:

Code:

   <Subsystem name="LiveTV">
      <Key code="Add" command="Channel+"/>
      <Key code="Subtract" command="Channel-"/>
      <Key code="Next" command="Channel-"/>
      <Key code="Prior" command="Channel-"/>
      <Key code="PageUp" command="Channel-"/>
      <Key code="PageDown" command="Channel+"/>
      <Key code="Return" command="ChangeChannel"/>

Why are "Next" and "Prior" both set to "Channel-" in these defaults? Are the names of these particular key codes just not intuitively named relative to what the Roku remote buttons actually do, or is something wrong here? What I mean is, logically, everyone who happened to look at these key mappings would intuitively think that one of these "Next and Prior" keys should be mapped to Channel- and the other mapped to Channel+, but practically, it doesn't seem to be operating that way.

Another thing that is confusing is that if I set PageUp to Channel+ and PageDown to Channel- it makes a long-press up-arrow *decrease* the channel, but a long-press down-arrow still also *decreases* the channel. So, now neither one *increases* the channel!

Also, doing this change seems to have no effect on the behavior of a long-press up-arrow or a long-press down-arrow on the Now Playing menu, which are the only things I want to reverse.

[mvallevand]

Those are questions for sub there is not documentation on any of this so some of it was trial and error. It does seem Next and Prior should be different, but it is not clear what triggers prior/next to even test if that is a problem.

As sub mentioned the UI client doesn't even know that this popup is active so it can't handle special cases and mapping the 11 keys on the remote to the 40+ keys on an MCE or Hauppauge remote has some compromises. In general I believe it works quite well. For the Roku the long keys you are using are only really only tested to change channels while watching live. I don't want to change the definition of channel up to change to a lower channel.

Sub is right that the best option is probably to increase the time of the long press, but I don't want to change the default since sending a short press when a long press is desired is not welcome behavior either. On my wish list for features that I'd like sub to add for UI client is to add a method to have custom expert settings stored in the clientstore file on the server. If that comes I will provide an option.

Martin

[sub]

Ah, I see. This is what I see for the defaults:

Code:

   <Subsystem name="LiveTV">
      <Key code="Add" command="Channel+"/>
      <Key code="Subtract" command="Channel-"/>
      <Key code="Next" command="Channel-"/>
      <Key code="Prior" command="Channel-"/>
      <Key code="PageUp" command="Channel-"/>
      <Key code="PageDown" command="Channel+"/>
      <Key code="Return" command="ChangeChannel"/>

Why are "Next" and "Prior" both set to "Channel-" in these defaults? Are the names of these particular key codes just not intuitively named relative to what the Roku remote buttons actually do, or is something wrong here? What I mean is, logically, everyone who happened to look at these key mappings would intuitively think that one of these "Next and Prior" keys should be mapped to Channel- and the other mapped to Channel+, but practically, it doesn't seem to be operating that way.

Another thing that is confusing is that if I set PageUp to Channel+ and PageDown to Channel- it makes a long-press up-arrow *decrease* the channel, but a long-press down-arrow still also *decreases* the channel. So, now neither one *increases* the channel!

Also, doing this change seems to have no effect on the behavior of a long-press up-arrow or a long-press down-arrow on the Now Playing menu, which are the only things I want to reverse.

Ignoring the Roku for a second...Unfortunately the app doesn't really know what type of remote you using, and different remotes had all sorts of different placement off buttons (including when CH- is above CH+, or whether it's the other way around). The defaults totally made sense for me on the remote I was using when I originally implement some of this. I know it doesn't always make sense on other remotes. This was part of the reason I originally created the KeyMappings.xml, so users could tweak things if they need to (however, whether that solution is workable when you add in UI clients is another question...)

They keycodes you see above, with names like "Next" or "PageUp" are microsoft names for keys on your keyboard. The command is how they'll behave in NextPVR.

Yes, having "Next" and "Prior" *may* be a mistake. I'm not 100% how to to generate a "prior" though. I think I have seen it in the past with some MCE remote, but with a quick check just now, I couldn't reproduce it. Somewhat oddly, Next and Prior don't go together. My keyboard generates "Next" and "PageUp" for the PageUp/PageDown keys.

In the case of these long-press keys. This isn't something NextPVR ever sees. This is done by the roku client, to try to squeeze more functions out of it's limited remote. ie, it either sends a one key to nextpvr, or another if you've pressed for a long time.

[BrettB]

Ah, I see. This is what I see for the defaults:

Code:

   <Subsystem name="LiveTV">
      <Key code="Add" command="Channel+"/>
      <Key code="Subtract" command="Channel-"/>
      <Key code="Next" command="Channel-"/>
      <Key code="Prior" command="Channel-"/>
      <Key code="PageUp" command="Channel-"/>
      <Key code="PageDown" command="Channel+"/>
      <Key code="Return" command="ChangeChannel"/>

Why are "Next" and "Prior" both set to "Channel-" in these defaults? Are the names of these particular key codes just not intuitively named relative to what the Roku remote buttons actually do, or is something wrong here? What I mean is, logically, everyone who happened to look at these key mappings would intuitively think that one of these "Next and Prior" keys should be mapped to Channel- and the other mapped to Channel+, but practically, it doesn't seem to be operating that way.

Another thing that is confusing is that if I set PageUp to Channel+ and PageDown to Channel- it makes a long-press up-arrow *decrease* the channel, but a long-press down-arrow still also *decreases* the channel. So, now neither one *increases* the channel!

Also, doing this change seems to have no effect on the behavior of a long-press up-arrow or a long-press down-arrow on the Now Playing menu, which are the only things I want to reverse.

Ignoring the Roku for a second...Unfortunately the app doesn't really know what type of remote you using, and different remotes had all sorts of different placement off buttons (including when CH- is above CH+, or whether it's the other way around). The defaults totally made sense for me on the remote I was using when I originally implement some of this. I know it doesn't always make sense on other remotes. This was part of the reason I originally created the KeyMappings.xml, so users could tweak things if they need to (however, whether that solution is workable when you add in UI clients is another question...)

They keycodes you see above, with names like "Next" or "PageUp" are microsoft names for keys on your keyboard. The command is how they'll behave in NextPVR.

Yes, having "Next" and "Prior" *may* be a mistake. I'm not 100% how to to generate a "prior" though. I think I have seen it in the past with some MCE remote, but with a quick check just now, I couldn't reproduce it. Somewhat oddly, Next and Prior don't go together. My keyboard generates "Next" and "PageUp" for the PageUp/PageDown keys.

In the case of these long-press keys. This isn't something NextPVR ever sees. This is done by the roku client, to try to squeeze more functions out of it's limited remote. ie, it either sends a one key to nextpvr, or another if you've pressed for a long time.

Looking at some Microsoft docs here: https://docs.microsoft.com/en-us/windows...-key-names, "PageUp", "Prior", and "PgUp" are all names for the Page Up key. And "PageDown", "PgDown", and "Next" are all names or the Page Down key.

[sub]

I think they do actually have separate keyboard scan codes though, which is probably why there is several names for them, even though they are for the same logical key.