So... Are we any closer to understanding why WB continues to target dopus.exe and what can be done about getting our favorite file manager off of WB's internal blacklist?

Neil had answered this issue before,its Opus's ends that causes this. 

I don't understand how it can be Opus's fault when Windowblinds triggers the exact same problems in completely unrelated programs if you simply rename them to dopus.exe, and when the problems that affect Opus go away if you rename it to something else.

Unless you mean it's Opus's fault that it is called dopus.exe

I'm sure there was a good reason/intention for handling dopus.exe in a special way at one point but, whatever that reason was, it is causing more problems than it is solving today. If there is still some problem with WB and Opus under normal circumstances (i.e. when WB isn't treating Opus specially) then I'll be happy to look into it on the Opus side.

Thanks!

Opus doesn't intercept/replace any dialogs; it just takes over the default filetype action for Folders, like an image viewer might take over the default action for JPEGs.

In particular, Opus does not intercept or modify the File Open dialogs in other apps. (People keep asking for it to, but that's a can of worms we'd rather not open.)

ID3 editing has moved from the viewer pane into the new dedicated metadata pane (which can also edit EXIF, PDF comments, file attributes, etc.):

I believe this might be the thread that Gaspershooters is referring to. https://forums.wincustomize.com/364637

Of the things mentioned in there:

- Opus no longer adds anything to the titlebars (as Neil says) so that's a non-issue now. (And WB skins Opus's titlebars anyway, so it's a moot point either way. )

- The resize grip on the glass status bar will look wrong with some themes, since Opus assumes the grip will be drawn on top of the background but some themes draw a solid square with the grip inside it. Users can turn off the glass status bar option in Opus if they are using a theme where that causes a problem. (Or even better update the theme to draw resize grips like the standard themes all do ).

One thing I noticed myself:

- While testing WB with dopus.exe renamed to test.exe, I also noticed an issue with one theme where the menus had extra lines around each item. We can fix that (and any similar issues).

It'll actually be really useful if WB treats Opus normally as it'll allow us to test our code against a wider range of themes than the ones that ship with Windows, since the Windows documentation about how you actually use the theme parts is non-existent, leading people to have to guess. For example, the menu issue I just mentioned is because Windows stretches the menu-item background across the entire menu, while Opus draws it for each menu item. Since the standard themes all have solid colours for those theme elements it's impossible to tell the difference between one arbitrary choice and the other. (It seemed like a sensible choice, too, since there is a separate theme element for drawing the menu border, which could've included the menu background if it was meant to be stretched across the whole menu.)

??

I was just updating/correcting the information in the older thread that got linked to. Didn't mean to look like I was hassling anyone; just providing information which I hoped would be useful, since I know not everyone knows Opus inside-out like I do.

(You should see the thread about this on the Opus forum where we got blamed for all the problems and lots of hassle even though it's completely outside our control.)

Far from it ... thanks for putting in the time to work out an issue. 

Thanks, guys!

As a test, this morning I made an experimental Opus build which patches Windowblinds in-memory to make it treat Opus like any other app.

The patching only affects the Opus process and will not modify behavior in any other program.

This is not intended as a long-term solution. It's so people can test what things would be like if Windowblinds was changed so that it does not detect Opus. In particular, it'd be interesting to know if this fixes garbanz0's toolbar/maximized problem (I've not been able to reproduce that myself so I don't know if it's related to WB or something else entirely).

This will only work with Opus 10.0.0.6 (beta). It won't work with older versions, nor with future versions.

• Download: (see readme in the archive if you need links to the 10.0.0.6 installer.)
  
  http://leo.dopus.com/temp/dopus_10006_experimental_windowblinds_patcher.7z
  
  
• Screenshots:
  
  Patch enabled: (full size)
  
  
  
  Patch disabled again: (full size)
  
  
  
  (You can use that registry value in the 2nd screenshot to enable/disable the patching. Restart Opus after changing it.)

Mine's 10.0.0.1.4145.x64 ....

Leo...I'd "ignore" garbanz0's issue as that will be due to an unauthorized 'patch' of the MS uxtheme.dll ....

thanks for that experiment, leo! it sure makes Opus play a lot nicer with WB. it's great to see menus, toolbars, and buttons skinned as they should be!

unfortunately it didn't fix the issue with the top toolbar that i have with some skins. this is one that gives me trouble, maybe you can install it and see if you can reproduce the problem. it would be great to finally get these guys off my back about the whole uxtheme issue...

http://tomrichter.deviantart.com/art/7zone-163832493 

anyway, i'm very glad to see an Opus dev working to sort this all out. thanks very much for your time and effort! 

So leads me to the question: Is the WB developer aware of this thread ?