I just downloaded a file in Firefox 130 to a folder on my NAS (a UNC path.) I have trouble running installers from UNC paths because of permissions, so I usually copy the file locally for an install. I asked Firefox to show me the file in folder and it brought my existing DirOpus 13.10 session active. It was already in that folder having been "left" there some hours ago. Because the file was new it wasn't listed in the "stale" folder contents, which of course causes the show feature to not work, and caused me some initial confusion about what was going wrong. (I tried a number of times, finally trying the find as I type, which also failed, before cluing in.)
Not sure what the theoretical correct behaviour is? Maybe a popup explaining that the named file is not in the current view, try a refresh?
That means the NAS isn’t generating change notification events.
Opus 13 has an option to poll specific folders every few seconds to work around the issue, which works well as long as there aren’t many things in/below the folder.
But most NAS should not have this problem, unless something like Docker is involved (since Docker breaks change notifications on Linux, so they don’t reach Windows either).
It’s also possible that Opus has been told not to detect changes on network drives, but that’s not the default. See the FAQ on folder change detection for more detail on that if needed.
I've no clue why there isn't a refresh notification when new files are written into the folder, but I don't particularly care to change my configuration in any way to fix it. I want DirOpus to not fail miserably in this circumstance all the same.
I think it would just be a work-around to rely on folder change notifications to "fix" the problem of being asked to show the location of a file that is not visible because the folder is in anyway stale. Firefox is explicitly asking DirOpus to do something and it explicitly fails to do it. I don't want excuses, I want it to either work (as in self-refresh) or to explain to me why it is unable to work (to give me the clue to do the refresh.)
Um, forgive me for being trite, but you sell DirOpus as a REPLACEMENT for explorer. So um, I expect it to WORK in place of it? That doesn't mean duplicating any bug it may or may not have???
Windows Explorer also does not update when new files arrive in the folder, and therefore also behaves incorrectly by not highlighting a new file when requested by Firefox.
I tried manually doing START | Run: explorer.exe /select,"\\NAS\Downloads\foo_.exe"
which doesn't exist and I get the same behaviour. (And it works right if I give it a file that does exist.)
Good point... maybe? Every time I've ever tried to get support here I get this same run-around. I will definitely remember this quality of support when it comes time to not renew my subscription.
Every time I've ever tried to get support here I get this same run-around. I will definitely remember this quality of support when it comes time to not renew my subscription.
I may have missed something, but see five issues, including this one, since 2015 for which you requested DOpus support:
In each instance, the team seemed to work with you in good faith and either asked clarifying questions or offered alternatives, then received no feedback on those good faith efforts.
The answer COULD be: we can reproduce this problem, but we don't intend to address it, sorry. The answer COULD be: We can't repoduce the problem, and we probably couldn't address it if we could. The answer SHOULD NOT be: "our software misoperates in your environment by design." (Aka, it's not our fault, it's yours.)
Also, thanks for doing the research into my posts that you think you did. Unfortunately, I have a large number of licenses, acquired in happier times (when I was less pissed off about my experiences here) and thus I have made other support posts on other accounts besides this one. (Which others those are aren't really anyone's business, they're separated the way they are by intent.)
And as for letting a thread die... well... I don't have infinite time or patience to be run around. I tend to fire and forget because I think my reports are clear enough and I provided enough info to investigate them. And I am about to do the same with this one because clearly expecting any other result was folly.
Could this be solved with a script add-in which on appropriate event (e.g., OnActivateLister or such) checks if the path is in NAS, and does a manual refresh if the path hadn't changed from before?
There is no need to give up just because some edge case caused by a third party misfunction is not covered by a default behavior of Opus (which aims to behave as consistently as possible).