When I first bought DO (v6 I think) one of the great features I remember it boasting is that each instance of DO opened in it's own thread so that if something went wrong with one windows, it would fall over without effecting the other windows (handy when you're in the middle of transfering files). These days i'm finding that when a DO windows stops responding and I have to end task, all of DO shuts down. Is there a way to get back the old behaviour? I'm finding DO less stable these days.
Opus is still as multi-threaded as it ever was (more so, in fact) - but what you are doing when you forcibly end the task is closing the process, not a thread. When you close the process all the threads within it are also closed automatically.
When a DO window locks up and will no longer respond, what is the best way to get rid of it?
The best way is to try to stop it locking up in the first place - if you have something repeatable that causes this then please do tell us so we can try and track the problem down.
Failing that, about all you can do is minimize the window and ignore it.
I feel pretty stupid for not having reported this earlier - I didn't realise I could reliably reproduce it.
Basically if I attempt to open a nonexistent network share (because I misstype the path, or the PC isn't turned on) by typing the path into the location, after about 15-20 seconds I get an error that the path was not found and if I choose "parent" or "cancel" the DO window stops responding.
This is where I would normally attempt to close the window and have to end the task. But just testing now I found that the window will start responding again after about 2 minutes.
I running 9.0.0.7