New SkinStudio 7 Pro beta on Impulse
Just a heads up that there is a much improved SKS7 beta on Impulse for OD Ultimate subscribers.
It adds an updated UI, UIS0 skin creation and lots of new Windows 7 theme parts.
Just a heads up that there is a much improved SKS7 beta on Impulse for OD Ultimate subscribers.
It adds an updated UI, UIS0 skin creation and lots of new Windows 7 theme parts.
I get the same Z71, but the tooltip background section does actually pop up on the right pane.
The edit tooltips section should not be there. The correct sections are on the Edit Treeview +/- controls page.
Ah, thanks!
Yeah it's always been checked, I've been getting the WB7 betas no problem.
SKS7 is listed as a separate app in Impulse, so you might have to scroll down a bit to see it.
Ah you're right...I see it now, installing. ![]()
I downlowded the new version yesterday.
Where did the alpha transparency button go?
I've been having to add it manually, code edit, to all my images.
On some images it adds it, but sets it to "0" by default. I have to manually change it to "1".
You should never have to manually add that.
Skinstudio will automatically add that value IF the image selected is a TGA and you have ticked the image has transparency box. If you select a bitmap then that value is set to 0 as bitmaps cannot have alpha.
Nice job on the update, Neil. I don't have any issues ATM, but I'll get back to ya! ![]()
OK. Figured it out. When adding a TGA, I de-select the transparency, then re-select it and it shows up correct.
I'll be honest, I'm not impressed with it being image aware. Have we become that lazy we can't check a simple box?
Why are you deselecting transparency?
It should automatically update when you change the image you are pointing to. How are you changing the image?
Regarding being lazy, it was a redundant option as there was never a case where you would want Trans and PerPixel to differ so it made sense to remove the option from SKS to avoid confusing users.
for some awkward reasons .. I not able to download it ![]()
serial you have provided can not be recognized ![]()
Do you have an ObjectDesktop registration or a SkinStudio one?
If you have an ObjectDesktop one then there is no need to manually enter a serial under registrations for SkinStudio 7 and if you do it might cause problems.
Neil, I think we're going around in circles over a non-issue. On a scale from 1 to 10, this is a -3. Not that big a deal.
The transparency thing. I add it from the dropdown list. It wouldn't change the code unless I deselected and reselected.
If I import, it would add it automatically. That's just how it's doing it for me. Don't know if that is how it was designed to work. Again, not that big a deal as long as I know when and how it's doing it on my machine.
As for the lazy, that was a rhetorical question, meant to be funny. I guess it didn't translate that way.
It's all good. Thanks for the assist.
I'm having a problem with the text margins on the Windows 7 taskbar buttons. The right and left margins don't seem to have any effect at all ![]()
Look at how the icon and text overlap the details on each end of the button ![]()

Here's how it looks on Vista

The taskbar button states seem to be mixed up when working with w7.
In XP & Vista, everything seems to be fine.
In W7, however, it seems as though the "highlighted & activated" state is being used instead of the "pressed" state.
The normal "highlighted & activated" state works fine, it just appears that the "pressed" state is being ignored and the "highlighted & activated" state is being used in its place.
Should this be happening?
I remember reading that there is no pressed state on win7 taskbar buttons.
If that's true, than that's pretty sucky. ![]()
One more thing:
In order for the show desktop button to blend into the taskbar, one has to add the line: BackgroundEffect=1 to the code section. There should probably be something in the extra tab to check off instead of adding the code manually
Bump
Also, can we have the favorites menu skinnable in Vista again? It used to be skinnable...now it's not. ![]()
I second that motion, not everyone looks in the codex ...and adding it manually shouldnt have to be done at all.
Consider this my daily bump
this is pretty cool, thanks for the inclusion.
Welcome Guest! Please take the time to register with us.