WindowBlinds -> DirectSkins question

Hello folks,

I purchased WindowBlinds. I have it configured to skin one application and that application works fine when skinned but only if I deselect:

WindowBlinds->BasicSettings->Skin Advanced Controls->Statusbar.

My old application writes a lot to the stausbar and explodes if I do not deselect this setting in WindowBlinds.

Not a problem you might say? Well it is because I can not distribute WindowBlinds with my app - so I am looking at DirectSkins, the distributable OCX skinning engine and I would have thought that there was a method that I could call on the DirectSkins OCX that would be the equivalent of deselecting Status bar skinning in WindowBlinds.

But, I can not find it and it's driving me batty so, if anybody can help I'd sure appreciate it.

It's almost enough to make me start looking at Codejock's XtremeSkins but I really do prefer DirectSkins!

I've exchanged emails with a sales guy here at Stardock but I really need to be talking with a techie.

Any help most apppreciated.

Cheers,
Simon aka WidgetBoy123
3,139 views 11 replies
Reply #1 Top
Hello Simon,

I will pass this on to our technical support and see if we can get you some help with this. They will get back with you as soon as they can!
Reply #2 Top

: Since DirectSkin consumers are businesses themselves, this is better handled through our official support channels. I have notified the DirectSkin support staff of your situation and they should be contacting you shortly (if they have not already).

Thank you,

-Mike
[Stardock Support]

Reply #4 Top
Please excuse my having posted this in a sibling forum here but I'm trying to understand if translucency works with DirectSkins? If I use a skin called 5imple Alpha with the retail version of WindowBlinds I see the translucent drop down menus.

If I take the same skin and use it with DirectSkins (the demo download version) the menus are no longer translucent when used with DirectSkins.

What's with that?

Any help appreciated!
Cheers,
Simon
Reply #5 Top
Per-pixel window borders and menus do not work with DirectSkin. DirectSkin essentially uses the WindowBlinds 4.6 engine, and per-pixel window frames and menus weren't introduced until WindowBlinds 5.
Reply #6 Top
Hi Mike,

I see, is there a roadmap for DS development / releases?
I'd like to know when an updated version of DS is going to be available such that it will be able to use per-pixel menus?

Is such an upgrade a trivial matter for the Stardock development team?

Thanks again for your kind help.

Cheers,
Simon
Reply #7 Top
I'm not a developer, but I do make skins, so I happened to know the answer to that question. For information about future updates, you should talk to the DirectSkin support folks as milksama suggested.
Reply #8 Top
It's a good idea - I just haven't got a reply from any technical folks so that's why I'm asking this forum so if anybody wants to tell me I'm all ears

Thanks,
Simon



Reply #9 Top

Right now we are working on support for 64 bit applications in DS.

We have discussed menu semi transparency and it is possible this will appear in future versions of DirectSkin but I cannot promise exactly when.

Regarding technical support, if you are already speaking to Larry it is probably best to continue like that.  He can forward mails to people like myself if he is not aware of the answer.

Reply #11 Top
I have a question regarding the Direct Skins method UxThemeEmulation:

The UxThemeEmulation method can be used to enable UxTheme emulation. If your application ships with a manifest then you should call this function when on WindowsXP. It alters the behaviour of DirectSkin so controls can skin correctly and also allows your app to use the standard Windows XP UXTheme functions to obtain skin information or to paint controls.

Does anybody know what this means?

I've tried using this method and I've tried examining the examples EXEs using a minifest file and changing XP's themes dynamically and I do not see any change in behaviour of any skinned apps.

I'd LIKE my Direct Skin skinned application to somehow be aware of and respect any Theme changes that users might make.

Any information about this would be most appreciated.

Thanks,
Simon