Quote:
Originally Posted by KevinH
Wow! I really thought that would do the trick. Maybe we should try adding a call to qApp->processEvents() before the sleep and shrinking sleep time down (all we really need to do is get time for other threads/processes to start).
|
You may be on to something, there! I added qApp->processEvents() before a 100ms sleep on the second try and everything seems to work. I added several css files and linked them all to the chapter file that I had open in book view and was able to delete them all successfully. Every single one after the first file needed the the second try to succeed, but they all were deleted.
Next I tried foregoing the second deletion attempt altogether and just put the qApp->processEvents()/100ms sleep before the one and only attempt to delete it. That worked equally well.
So what's your advice? Limit the processEvents/sleep to the second deletion attempt after a failure? Or a wholesale processEvents/sleep with one, and only one, deletion attempt? The former would likely limit any potential delays to the Windows platform since the other two platforms don't seem to need the backup. It seems more robust to me, as well.