After deleting a subfolder, it remains visible.
I may select any other folder in the folder tree (hoping the foldertree will refresh) but the subfolder remains visible.
Tried that a couple of times.
Clicking on the 'deleted' folder results in an 'Error reading folder' pop-up.
Abort +selecting another folder, the deleted folder is still there.
Eventually, F5 solved it.
Then again, I would assume the deleted folder would disappear after a short while or when clicking on another folder in the tree?
further to the above: when I click on a non existing folder in the Recent-list, I get the same error, but immediately after selecting another folder, the non existing folder disappears from the list, rightfully so. wud expect same behaviour with 'normal' folders.
If you open two separate windows showing the same folder, then delete the sub-folder from one of them, does the file display in both windows update? Or does only the window where you deleted the folder update?
Does this happen in all folders, e.g. if you type /desktopdir and push return, then create and delete a folder there, does it also happen? Or is it only happening in certain places (e.g. the My Music folder under your name in the tree, if I'm guessing correctly?)
Opening 2 sessions of Opus, deleting a subfolder in one of them. The subfolder remains there. Click on the 'deleted' subfolder->2x 'Error reading folder'-pop-ups . Click 2x Abort. Folder still there. In both sessions, go to another folder. No change. Even not after 5 minutes. 2x F5 solves this.
As for the 2nd thing: I donot have desktop in my folder tree, can't tell, sorry.
(old thing, messes up my lister)
[quote="leo"]Is stays there just in the two folder trees, or also in one or both file displays?
What if you also open an Explorer window, then delete in Opus; does Explorer notice the change?
Using desktop was just an example. Please try with folders in other locations and tell us about where the problem does & doesn't occur.[/quote]
Q: Is stays there just in the two folder trees, or also in one or both file displays?
A: both folder trees
Q:What if you also open an Explorer window, then delete in Opus; does Explorer notice the change?
A: when I have Opus foldertree open and on top Windows Explorer and delete a folder in Explorer, then Opus is updated immediately
Q: Please try with folders in other locations and tell us about where the problem does & doesn't occur.
A: I created a new folder and deleted it immediately thereafter, then the folder disappears immediately. I did this a few times.
Empty folders and a folder with a couple of files.
Oh, btw and FWIW..
in addition to the F5-solution: if that one does not work
(happened to me a couple of times times, hitting F5 a dozen times, in vain),
then : exit/relaunch Opus.
If anyone wants to answer my questions, we might be able to work out what's going wrong. If not, nothing's going to happen unless we randomly stumble on the same problem ourselves.
when selecting a folder in the folder tree (left window panel), delete it, it remains in place, albeit, with an error (cannot read folder) when selecting;
when 2x instances of Opus active, delete a folder in the 2nd Opus instance, 1st Opus session in the background, no changes to either 1st of 2nd session, folder remains visible, 'cannot read'-error;
when using Windows Explorer, folder is gone/disappears immediately
sometimes hitting F5 solves this, sometimes not
if not, then exit Opus, relaunch
note: weird thing is, with me, when i create a new folder delete that, the folder is gone.
maybe this is the reason why it is difficult to reproduce...
Encountered the problem when reorganizing old stuff.
It is hard to replicate. I've had the same problem, though it was fixed, but it wasn't. I ended up uninstalling and reinstalling Dopus, then changed some settings in my tree (which folders were shown, like libraries, recent folders, etc.) but I can't remember what exactly I changed. And honestly, I'm a little scared to test what setting it was, afraid to re-introduce the problem.
Heh, i don't mean to be rude, but i think you have enough answers.
But if you do not want to reproduce it by yourself (you/your company coders/whatever) for years (2-3 years for me or even more)... then it's just a useless topic.