[quote who="c242" reply="91" id="3055642"]But I also think this should have been kept on an internal level[/quote] This quote from Stardock's CEO seems appropriate here: [i]In the case of Stardock, it means that the company reflects my values. In particular, transparency and collaboration with others. Transparency is a double-edged sword. We won'
This problem seems to have gotten worse. We just got a report via the Directory Opus support channel that the File Open dialogs are not showing up *at all* in Opus when WindowBlinds is installed. Installing the latest WindowBlinds (from CNet, signed by Stardock on 10-Nov-2011) on a test machine (Win7 64-bit) confirmed this to be the case. Any action in Opus which is meant to trigger a standard file dialog now does nothing. EDIT: Some of the Aero-based themes appear to
[quote who="c242" reply="61" id="2955178"]Leo : Does the new official update (10.0.1.0) contain these fixes ?[/quote] It doesn't. Having confirmed what/where the problem is, we're leaving it up to Stardock to fix Windowblinds, rather than making Opus patch their code.
[quote who="Neil Banfield" reply="57" id="2951706"]Sorry I have not posted before but I am currently working on another project. It looks like we should remove dopus from the internal exclusion list in the next update then.[/quote] Thanks Neil!
[quote who="garbanz0" reply="47" id="2950522"]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
[quote who="c242" reply="48" id="2950547"]Hm, does this work with a german Version also ?[/quote] Yes, it should work fine with the German version. (All the language strings etc. are in a separate DLL.)
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&
[quote who="Gaspershooters" reply="38" id="2949396"]For the record,extremely persistence would only get ignored/put it on the back burner................................... [/quote] ?? 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 ab
[quote who="Lantec" reply="35" id="2948966"]I believe this might be the thread that Gaspershooters is referring to. https://forums.wincustomize.com/364637[/quote] 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
[quote who="Jafo" reply="32" id="2948813"]I'll point Neil at this thread for his input[/quote] Thanks! [quote]but I am guessing the 'problems' seen by notepad being renamed to dopus, etc is the 'necessity' that dopus be excluded from WB due to how dopus intercepts or replaces some of the explorer dialogs....[/quote] Opus doesn't intercept/replace any dialogs; it just takes over the default filetype action for Folders, like an imag
[quote who="Gaspershooters" reply="29" id="2948489"]Neil had answered this issue before,its Opus's ends that causes this.[/quote] 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 :
[quote who="Jafo" reply="22" id="2947926"] Quoting LeoDavidson, reply 21Opus doesn't patch msstyles at all. LeoDavidson....'msstyles' IS the 'patch' ...it's a 'hack' of an MS dll to allow the use of unsigned styles - a breach of the MS EULA.... Windowblinds is like Dopus...it's legit software....[/quote] Ah, okay. I thought you meant somehow patching C:\Windows\Resources\Themes\Aero\aero.msstyles or similar.
[quote who="DrJBHL" reply="17" id="2947289"]Leo, that's great news... thank you very much for clearing that up. By its own skins I mean that in DOpus Forums there are various skins available.[/quote] Those skins are just bitmaps (and sometimes some XML that tells Opus where to use them) that get used for the background of certain elements instead of asking the theme to draw the background. Shouldn't cause any problems with Windowblinds. [quote]When you s
[quote who="Lantec" reply="9" id="2946890"]Just out of curiosity how often do you add new certificates? Until today I've looked at that dialog exactly 1 time....now twice.[/quote] It's not just that dialog; that dialog is just an easy to see example of it. It seems to be any File Open dialog opened by any exe called dopus.exe. Here's an example where I took a very simple app/UI I wrote, that uses no custom 'skinning' code whatsoever and is just an MFC UI I
[quote who="Jafo" reply="11" id="2946898"]WB skins [components of] the Explorer shell. Dopus can be set to 'replace' parts of that Explorer shell.[/quote] No, Opus is NOT a shell replacement like Litestep. Opus only 'replaces' Windows Explorer, the file manager, not the shell. And all 'replaces' means in this context is that it takes over the filetype association for folders so that when a folder is double-clicked (or whatever) the folder