Posts: 23
Joined: Jan 2013
Reputation:
0
+1 for being able to disable confirmations here
Posts: 279
Joined: Feb 2011
Reputation:
2
I don't agree that the old Frodo method of just deleting everything when the Source is disconnected/offline is something anyone wants...
I feel that XBMC should be made simple and only identify when all / most entries in the library are missing suddenly, and interpret that as NAS being down / offline, and ask user if he wants to empty library. In cases with just one or a few movies missing they should simply just be removed automatically without bothering the user.
Sounds OK to people?
Posts: 31,445
Joined: Jan 2011
That sounds a lot more complex to code into XBMC for testing if a source is offline.
Posts: 5,284
Joined: Jul 2012
Reputation:
343
2014-05-29, 10:31
(This post was last modified: 2014-05-29, 10:34 by scott967.)
This sort of thing is common in Windows at least. When it wants a confirmation you have options no, yes for this, yes for all. I can see the idea probably was in case a source is accidentally offline/unreachable you don't want to blow away your whole library . The current method I kind of like as it confirms that it is cleaning up a folder, but I haven't tried to do it with more than 1 or 2 folders deleted so it hasn't been an annoyance.
scott s.
.
Posts: 1
Joined: Jun 2014
Reputation:
0
I was looking at the ticket and since there doesn't seem to be a way to comment on that directly(or any comments from the developers as to what is planned), I'll share my thought here.
The simple way around this would be to test that the drive is online first. If the drive is online, proceed with the cleaning and don't prompt, or prompt and give the user the option not to prompt. If the drive is offline, ignore any entries from that drive, unless of course that drive had been removed from the source list entirely. I had that problem when retiring a network drive and moving stuff to a new network or local drive shortly after updating to Gotham.
Posts: 31,445
Joined: Jan 2011
This is basically what happens, or what is supposed to happen. The multiple prompts is a bug. XBMC tests to see if the whole source is off line or if it is just one file, then should prompt which should include the entire source, rather than several prompts.
I'm not sure if the issue is in how XBMC tests or how the prompts are handled or what, but Montellese is on the case. The issue here seems to be that two different bugs are happening, one that has been identified, and one that hasn't been reproduced yet.
bthusby, could you get us a
debug log (wiki) of when you trigger this issue and then upload the log directly to the trac ticket?
Posts: 17,859
Joined: Jul 2011
Reputation:
371
Fix may come in 13.2 (or maybe only in 14.0 depending how big the changes are)
Posts: 90
Joined: Aug 2012
Reputation:
0
+1 for disabling confirmations.