Jump Directly to Particular Section of XNEWA

[pkscout]

I've modded Confluence to provide an option to use the XNEWA screens instead of the default Confluence ones when clicking from the various submenus in the LiveTV section. The only thing is that when you, for instance, click on Recordings, you get taken to the main XNEWA screen. Is there some way to call XNEWA and tell it on which item I'd like to start? It's not a big deal, but it would make the user interface nicer. Right now I have to select Timer in Confluence and then click down to the right place in XNEWA.

Mahalo.

[mvallevand]

I could but what is the use case? There is overhead to having the PVR addon enabled so why would you not want to use the PVR add on functionality?

Martin

[pkscout]

I find the native timer listing in XBMC to be less than helpful. It lists only the next occurrence of a recurring recording (so, for instance, I see that the news is being recorded tonight, but it's not on the list for tomorrow). And if you click on a timer you get the XBMC window for editing the timer rather than the nice one that NPVR provides. I agree that the EPG listing and recording listings in XBMC are probably fine, but the timers is the stickler for me. If the functionality was there, I was going to use it, but unless you're completely bored, I don't see any reason to add it.

[mvallevand]

I find the native timer listing in XBMC to be less than helpful. It lists only the next occurrence of a recurring recording (so, for instance, I see that the news is being recorded tonight, but it's not on the list for tomorrow). And if you click on a timer you get the XBMC window for editing the timer rather than the nice one that NPVR provides. I agree that the EPG listing and recording listings in XBMC are probably fine, but the timers is the stickler for me. If the functionality was there, I was going to use it, but unless you're completely bored, I don't see any reason to add it.

It is a trivial 5 line change. Replace default.py with the file in the attached and see how it works. To invoke from the skin I suspect something like this would work.

<onclick>XBMC.RunScript(script.xbmc.x-newa,upcoming)</onclick>

Martin

[pkscout]

That works perfectly. Now that I see the code logic, I might add some other entry points.

[pkscout]

OK, I added all the other "logical" entry points. There are now entry points for the list of recurring recordings (schedules), the NPVR EPG (epg), the list of recordings (recordings), and the web client (webclient). I've attached the updated default.py in case you want to use it. I mostly did it for completeness and because the Confluence mod I did allows you to decide what parts of XNEWA you want to use instead of the native XBMC stuff.

https://github.com/pkscout/skin.confluence.gotham.mod

There are a bunch of other mods in there. The NextPVR ones are the last set of commits.

[mvallevand]

OK, I added all the other "logical" entry points. There are now entry points for the list of recurring recordings (schedules), the NPVR EPG (epg), the list of recordings (recordings), and the web client (webclient). I've attached the updated default.py in case you want to use it. I mostly did it for completeness and because the Confluence mod I did allows you to decide what parts of XNEWA you want to use instead of the native XBMC stuff.

Ok I included that in 2.3.0 which I just uploaded. Feel free to rewrite any of the list skins in x-newa for Confluence, it is been on my to-do list a little too long.

Martin

[pkscout]

Ok I included that in 2.3.0 which I just uploaded.

I noticed this morning that I still didn't have X-NEWA 2.3.0 (I have the repo installed). I grabbed the zip file of the update from epgtools and noticed addon.xml still has 2.2.9 in the version string. So I suspect folks updating from the repo haven't gotten the update yet.

[mvallevand]

I noticed this morning that I still didn't have X-NEWA 2.3.0 (I have the repo installed). I grabbed the zip file of the update from epgtools and noticed addon.xml still has 2.2.9 in the version string. So I suspect folks updating from the repo haven't gotten the update yet.

Thanks it should be okay now.

Martin