X-newa 2.5.2 Release

[fred250]

@Martin

Slightly off topic...
You may use the screen property of /activity to have the FF/RW buttons do different things in different plugins depending of whichever function is the most important.
Like using them for pgup/pgdn in recordings but still navigating blocks in TV guide.

/Fred

[mvallevand]

Thanks Fred, I was looking for a solution that would work for all web clients which should be as dumb as possible, so that people can go back and fourth between Kodi, nlite (which will be a great client), and your RPi client. I think my keymappings.xml probably makes more sense even in NextPVR. It allows navigating TV in blocks, works the same in media and adds function in sub's UI.

However you got me thinking and in the next beta I think I will add a popup windows on the Kodi context menu key to provide some more keys for general use.

Martin

[SteveTyrakowski]

Thanks sub,

@Steve the change allows you to configure how the FF/RW keys work in the UI and to configure them to function as page up/down keys. The attached updated KeyMappings.xml wll do the trick if you use the NextPVR defaults.

That being said, I personally use my Rii wireless keyboard with most devices with reduced remotes. I have both Bluetooth and 2.4Ghz and they both work great with the AFTV and allow percentage jumping. If you'd like with a change to web client I could probably accept a longpress that you could map to the 5 or 6 key to jump in the list, if you want to read up on doing that http://kodi.wiki/view/Alternative%20keym...%20remotes

Martin

I tested out the keymap change using the XNEWA web client on the AFTV with Kodi and the FF/REW keys now do the PGUP and PGDN, but I'm seeing it move two pages at a time.

I copied the NextPvr.exe that sub posted to the \Program Files (x86)\NPVR folder. I was having a little trouble where XNEWA did not want to start up, so I unloaded the NTray and restarted the recording service and then when I got XNEWA to start up, it killed the device status screen on the NextPvr computer. When I restarted again and got the device status open Again I could no longer start up XNEWA on the AFTV. So then I rebooted the NextPvr computer and now it seems to allow me to run XNEWA and it does not kill the device status.

A huge improvement having the page up/down capability again. The double page move is almost better for me since I have so many recordings.

Thanks
Steve Tyrakowski

[mvallevand]

After a server restart I find there always is an issue starting web clients because of IPC problems on the server. Usually it will settle down after 3 or 4 404 errors but I have seen it go up to 19. That doesn't explain the problems you had though. Your logs might help here if you are interested. It might show why you are getting double pages, I don't see that here.

Martin

[mvallevand]

I have update post 1 with a new version that provides many additional commands on the context menu in UI, thanks to Fred's suggestion. I would be interested in feedback. It is mainly for limited remote users especially in the TV Guide, but the quick key for recordings and the guide might be handy for everyone who doesn't have FN key access. I kept the numbers on the main meu since an up arrow will make it easy to do percentage skips in long lists where paging is a nuisance.

- Web client new context menu
- Web client progress spinner on open
- Estuary skin dialog background change

Martin

[SteveTyrakowski]

I have update post 1 with a new version that provides many additional commands on the context menu in UI, thanks to Fred's suggestion. I would be interested in feedback. It is mainly for limited remote users especially in the TV Guide, but the quick key for recordings and the guide might be handy for everyone who doesn't have FN key access. I kept the numbers on the main meu since an up arrow will make it easy to do percentage skips in long lists where paging is a nuisance.

- Web client new context menu
- Web client progress spinner on open
- Estuary skin dialog background change

Martin

It works great. The only suggestion I have to make it even friendlier is if you could make the options in a 3 or 4 wide grid instead of a list to reduce the number of clicks to get to your desired key and it could look like the button layout of a remote and more options would be visible without scrolling.

Thanks for the work on this it has made the AFTV remote much less painful.

Steve Tyrakowski

[mvallevand]

Thanks for the feedback, unfortunately Kodi doesn't have a grid dialog. It may not be intuitive but you can use the up arrow to reduce the number of key strokes Also reordering the two menus might help let me know your ideas on what the most used keys will be. The paging keys keys don't help because of the list size so I might play around here,

Martin

[SteveTyrakowski]

Thanks for the feedback, unfortunately Kodi doesn't have a grid dialog. It may not be intuitive but you can use the up arrow to reduce the number of key strokes Also reordering the two menus might help let me know your ideas on what the most used keys will be. The paging keys keys don't help because of the list size so I might play around here,

Martin

yes I use the up arrow trick. No big deal. As you said, the list is not that long. Maybe put the numbers on a submenu if the list gets any longer. I'm most likely to just use the numbers, and then I'm most likely to use the high numbers so the up arrow will work well for most of what I do. I'd probably just do a bunch of page downs rather than go to the menu to press the 3 or 4.

When in the context menu, do the left/right keys do anything? Perhaps they could be something like 3 up or 3 down. that would give the same benefit that a grid would as far as saving clicks.

Steve Tyrakowski

[mvallevand]

When in the context menu, do the left/right keys do anything? Perhaps they could be something like 3 up or 3 down. that would give the same benefit that a grid would as far as saving clicks.

They highlight the Scroll bar and Cancel so up-right-left will get you to 3 fastest. The advantage to using this menu to navigate is it is faster then NextPVR sending screens.

Martin

[cncb]

In 2.4.8 you added a 1.2-second delay in emulate.py before sending the CTRL+F5 keypress after playback stop to help with the refresh timing of my plugin. This seems to be missing in the new version so it would be great if you could add it back. Thanks.