TV Guide Recording Buttons Out of Sync with Actual DVR Recording Status

[sub]

In your logs, it seems to only take a few hundred milliseconds from the request to cancel the recording, to it being cancelled.

Just curious, if you'd instead cancelled from the Scheduler page, and then got back to the TV Guide page (with that most recent listing-details-modal.js installed), does it now behave the way you expected? (ie, is it only when cancelling from the Guide page itself)

the computer is dedicated to running NextPVR without also being a home-networked media host etc, a mostly idle dual core Intel Core i7-3520M generally using 2.5GB out of 8GB of physical memory

Yep, absolutely no problem with those specs.

[mvallevand]

This was the dynamic update I was talking about.  

Martin

[LinuxDVR]

In your logs, it seems to only take a few hundred milliseconds from the request to cancel the recording, to it being cancelled.

Just curious, if you'd instead cancelled from the Scheduler page, and then got back to the TV Guide page (with that most recent listing-details-modal.js installed), does it now behave the way you expected? (ie, is it only when cancelling from the Guide page itself)

the computer is dedicated to running NextPVR without also being a home-networked media host etc, a mostly idle dual core Intel Core i7-3520M generally using 2.5GB out of 8GB of physical memory

Yep, absolutely no problem with those specs.

Yes, if I cancel from Scheduler page and navigate back to guide.html the Record button displays as fast as I navigate there. It is only when cancelling from guide.html that it takes 30 seconds before the Record button will display again upon manually refreshing guide.html. 

When I click the Cancel button from guide.html, as you mention it only takes milliseconds for NextPVR to cancel the recording - yet it is the 30-second delay after the recording is cancelled before guide.html will display the Record button again that may be solved with a button click event on the guide.html Cancel Recording button or similar to call the code routines like pollForRecordingChanges - that would be icing on the cake to adjust that, but it is great that you provided the revised javascript file so quickly, and I now know which order to use the web pages to create the functionality for now.

[mvallevand]

As I noted that cancel then record use case is really for testing so 30 seconds is not a big priority. Just use a UI client when you want to test this scenario 

Martin

[sub]

Despite repeated attempts here, the scenario you're describing is working fine for me, but I'm guessing it's a timing thing. I've attached an another listing-details-modal.js, which has another attempt at addressing it. Let me know how you get on.

[sub]

Actually, try these instead. This is a better way of doing it.

[LinuxDVR]

< Edited to correct incorrect posting >

I edited this post since it was incorrect info, must have been too early in the morning and I wasn't testing what actually creates the issue. The latest html and js still have the ~30 second delay before the Record set of buttons will display rather than the Cancel button for the recording that was already cancelled. I'll try again later and post the logs, but at least I have a workaround in the mean time. Thanks!

[sub]

Great