Search list not updated afer recording cancelled

[pabaxt]

This seems to have appeared in the latest release. I search for a show title where I only want to record certain episodes. I click on the episode and hit Record Once - the lentry turns red as usual. So far so good.

Then I realise I selected the wrong episode so I click the line again and click Cancel Recording. The list is not updated so still shows Red and if I click the entry again it still shows the Cancel button, but in fact, the recording has already been cancelled, it's just that the list has not refreshed. If I Manually refresh (by clicking Search Guide) again, it shows that the episode will not be recorded.

[mvallevand]

This can be duplicated in the web client (best to specify the client you use) and it can also occur on a previously scheduled recording found during the search. The error does show in the browser window too, line 256 of listing-details-modal.js needs to be reloadRecordings();

The file with the problem hasn't changed since November

Martin

[sub]

This can be duplicated in the web client (best to specify the client you use) and it can also occur on a previously scheduled recording found during the search. The error does show in the browser window too, line 256 of listing-details-modal.js needs to be reloadRecordings();

The file with the problem hasn't changed since November

I've fixed this for the next build.

[sub]

This seems to have appeared in the latest release. I search for a show title where I only want to record certain episodes. I click on the episode and hit Record Once - the lentry turns red as usual. So far so good.

Then I realise I selected the wrong episode so I click the line again and click Cancel Recording. The list is not updated so still shows Red and if I click the entry again it still shows the Cancel button, but in fact, the recording has already been cancelled, it's just that the list has not refreshed. If I Manually refresh (by clicking Search Guide) again, it shows that the episode will not be recorded.

I wasn't able to reproduce this in my build, but I suspect it was fixed by another change I made a couple of days ago.

[pabaxt]

Thanks, guys, I confirm it is now fixed. Apologies for the delay in responding and mentioning it was the Web client.

As always all your effort on such a great application is much appreciated.