Part of the problem is that Samba is likely to only be tested against Explorer so unless Opus does exactly what Explorer does (which isn't documented) things can still go wrong through no fault of Opus.
(Although I don't know if that is what's happening here... I'm just saying, "it works in Explorer" doesn't mean a lot as everything is tested against Explorer. Heck, there have been preliminary versions of Explorer which broke against Samba (and other non-MS SMB servers) and meant Microsoft had to go back to the old way of doing things, so even Explorer can be affected.)
I could equally say that Opus works fine against Windows network shares -- and Opus has no idea about which OS is on the other end of the network and doesn't do anything different for different servers -- so the problem must be Samba. In reality it could be either program doing something wrong but, at the end of the day, Opus is just using the Windows API which Samba is trying to emulate.
Anyway... FWIW, I have used Opus against Samba shares and not had a problem renaming files so it should be possible to fix things. Make sure it's a recent version of Samba (newer versions are much, much better than older ones), maybe check that it's one which handles Unicode properly, and check its configuration file for how often it sends change notifications (or if it sends them at all).
[quote]Part of the problem is that Samba is likely to only be tested against Explorer so unless Opus does exactly what Explorer does (which isn't documented) things can still go wrong through no fault of Opus.
[/quote]
Yeah that would be a big problem, considering that DO is supposed to be a replacement for Explorer, so you'd think you'd be testing it not only against Windows machines, but against other OSs implementing Samba as well.
When it comes to almost everything in life, it's all about perception. And in the case of your application, you can jump up and down all you want and say hey, it's Samba's fault, but in the end, it still boils down to a customers perception of your software. And when it comes to interacting with various systems, applications, OSs, well the fact is at some point you have to include workarounds to over come the short comings of these "other" systems/code.[/quote]
BTW, I wanted to make sure we're clear on the rename issue. After the file rename, the name I see IS the new name. I just see 2 files in the list in DO with the same name.
So if I've in a folder that contains 1 file named OLD.txt and I try to rename it to NEW.txt I'll see 2 files with the name NEW.txt. When I hit F5 I then only see 1 file.
Opus is not my application. This is a user-run support forum.
Opus is tested against all kinds of things, including Samba shares where, in my experience, it generally works if the Samba share is behaving.
I'm not saying what you are seeing is definitely Samba's fault. I don't know. But there are problems in this area which some versions/configurations of Samba do cause so it makes sense to look at those known issues first.
Even if it is Opus's fault, how do you expect anyone to fix it without any investigation of what's behind the problem? You seem not to want to bother investigating those things and instead just want to say it's Opus's fault as if attributing blame will magically solve the problem.
As I said, Opus works with Samba in general. If it isn't working with a particular Samba server then the reason why needs to be investigated. If something is discovered which could be improved on Opus's end then it surely will be, but without investigation on your end, just knowing that Opus + your particular Samba server that nobody else has access to doesn't work isn't anything to go on.
If you try the things suggested in this thread, and in the FAQ, and it still doesn't work then we can investigate further, but if you just want to argue about which piece of software is probably at fault without actually trying any of the suggestions or debugging steps then I don't see the point of this discussion.
I pointed to a FAQ which describes how to enable the notify_debug setting in Opus to help understand what's happening when change notifications are missed. That's a good first step if you want to get to the bottom of what's going wrong.
People on this forum are quite active in trying to reproduce problems for other users... So if you go through the FAQ related suggestions and provide some qualitative info (basic stuff like Linux and Samba versions and possibly config file contents), you'll probably find some folks here trying to help. GPsoftware in turn make huge efforts to add options that are often times relevant to only a small subset of users, but the first step is usually helping others help you...
In reality it could be either program doing something wrong but, at the end of the day, Opus is just using the Windows API which Samba is trying to emulate.