Fixed : Bugs with Macromedia software - cheers Stardock :)

EDIT: Having updated to the latest beta, it seems that all of the issues I was having with Macromedia products have been sorted out.. I haven't tested it thoroughly yet, but fair play for clearing that up - it was unexpected! :D




Having tried everything I could think of, and not getting anywhere in particular, I've pretty much given up on trying to get Macromedia apps like Dreamweaver / Flash / Fireworks to skin properly (at least for now).

However, when setting up the application exclusions, the ONLY way I could get any change at all was to completely ignore the application in its entirity. None of the other settings, such as "Only skin this applications title bar" had any effect. This is at least true in the WB5 beta.. I've only recently started using Windowblinds, and although the same problems were in 4.x, I didn't try setting up the exclusion, and I'm a bit dubious about downgrading just to test it.

Firstly, does anyone know if there is any way to at least skin the title bar in these apps with everything else defaulting to 9x style? (I've tried pretty much every combination of uninstall / reinstall with no effect)..

..and secondly, does everyone who uses these applications have the same problems? (Including the broken app exclusion, and the knackered skinning of toolbar frames etc - ie toolbar title frames are black and tab backgrounds are red for ALL themes, as long as WB is running)

Reason I ask, is if everyone has the same trouble, I doubt there's not much can be done.. but if some people can get things working normally, there should be some way of working it out.. which is something I'd like to do, otherwise it's going to be the case of having to go back to msstyles for 75% of the time I'm using my computer, which pretty much negates any reason for having just spent my money on this app (especially frustrating as the new features in WB5 look great!)

There clearly has to be some way of fixing this, otherwise custom msstyles would suffer the same ill effects (which they don't)..

So erm yeah, let me know your experiences, and I'll see if I can find a remedy.

Edit : It's also worth noting that the problems are still there, even when using an msstyle, when WindowBlinds is loaded. The only way to get around it is to completely unload WB and use uxtheme.. which is.. erm.. rubbish heh.
2,491 views 5 replies
Reply #1 Top
FWIW I'm using the WB5 beta with the Arrow skin & it's skinning Studio 8 apps fine as far as I can see (though I've only just installed my Studio upgrade a couple of days ago). I don't remember having any exclusions set up for my Macromedia programs before. If I did it was probably for Dreamweaver & it must have worked as there was nothing annoying me about the interface.

Posted via WinCustomize Browser/Stardock Central
Reply #2 Top
Yeah.. I think it probably looks fine to you as the Arrow theme is generally based around black.. which is one of the main colour problems in the Macromedia apps..

I found another post with a similar problem - check it out for examples

Link

I know it's not a major major issue (although the "only skin titlebar" thing is slightly more pressing).. but it is rather distracting if you're using a lighter theme
Reply #3 Top

Only skin titlebar means disable WBs non themeaware skinning code.

As the macromedia apps are theme aware, their controls continue to skin in skin only titlebar mode.

Reply #4 Top
I use FWMX2k4 a lot. Some skins, in the past, have looked just terrible on Fireworks, but lately I have had no problem. Certain parts just don't get skinned, it seems, like the title bars for the panels.




Is this what you are referring to? I have noticed this, but with most windowblinds it is OK. It'd be cool if macromedia products were fully skinned, but I think it's MM's problem, not WindowBlinds. Personally, I use WB all the time, I don't even know what these apps look like without it.
Reply #5 Top
Ditto on the "I don't even know what these apps look like without it"! I never actually noticed the "red & black" issue as a problem, but yes I get it too.

Posted via WinCustomize Browser/Stardock Central