SKS and/or WB Coding Issue

from WinCustomize Forums

Getting tired of this, but while I am designing a WB skin strictly for Windows 7, I have to manually go into the skins .UIS file and delete the File= on [XPShell] and [ToolbarIcons].  As I understand these items do not apply to a Windows 7 skin, yet SKS or WB, (not sure which), keeps adding those File= lines back in even though I delete them and save the file.  Heck, the file names being added do not even exist!  What the heck is going on here?

[XPTaskbar]
File=Omen\XPStuff.xp

[XPShell]
File=Omen\Omen.xps

[Animations]

[ToolbarIcons]
File=Omen\Omen.toolbarIcons

6,248 views 12 replies
Reply #1 from WinCustomize Forums Top

Does it mess up the skin? Nah, it doesn't.
Have Stardock been littered with complaints about this? Nah. First time it's been mentioned.

Is it really an 'issue'? Nah, not really. ;-)

 

But if you really, really, -really- wanna get rid of them, just simply open the .uis in notepad and edit them out.

You're welcome. ;-)

(There are tons of lill nagging issues with SKS, that hasn't been fixed over the years.)

Reply #2 from WinCustomize Forums Top

Quoting Snowman, reply 1


There are tons of lill nagging issues with SKS, that hasn't been fixed over the years.

It's been a good opportunity to fix them no ? (as well as the rollsize value ... )

Sins of a Solar Empire: Rebellion
Reply #3 from WinCustomize Forums Top

Quoting Snowman, reply 1
Does it mess up the skin? Nah, it doesn't.
Have Stardock been littered with complaints about this? Nah. First time it's been mentioned.

Is it really an 'issue'? Nah, not really.

 

But if you really, really, -really- wanna get rid of them, just simply open the .uis in notepad and edit them out.

You're welcome.

(There are tons of lill nagging issues with SKS, that hasn't been fixed over the years.)

 

Yeah, I know that issues have been there for years, tons of them, and it's really sad no one fixes them Snowman, very sad.  Also, I mentioned in the OP that I do edit them out and save the .UIS file, but as soon as I open SKS again to work on the skin some more, it puts those statements right back. :S

 

Tip to Stardock... perfectionism is the key to success. :)

Reply #4 from WinCustomize Forums Top

Do not delete those lines.  They are not doing you any harm and do not make your skin any less Win7.

If it hurts every time I poke myself in my eye then the solution is to stop poking myself in the eye.  The same is true here.  If the lines keep coming back after you delete them then perhaps there is a reason why they are coming back and you should stop deleting them...

Reply #5 from WinCustomize Forums Top

Have you Checked this Correctly :maybe:

Reply #6 from WinCustomize Forums Top

Quoting neone6, reply 5
Have you Checked this Correctly

Not if you wanna skin Vista and/or XP......

Reply #7 from WinCustomize Forums Top

Getting tired of this, but while I am designing a WB skin strictly for Windows 7, I.....
<_<

Reply #8 from WinCustomize Forums Top

Thanks for the information Andrew, but setting that to Windows 7 only made no difference.  I guess I will just have to live with yet another SKS issue like Neil referenced to, along with the many other issues SKS has that you have to work around.  :S

Reply #9 from WinCustomize Forums Top

Quoting LightStar, reply 8
Thanks for the information Andrew, but setting that to Windows 7 only made no difference.  I guess I will just have to live with yet another SKS issue like Neil referenced to, along with the many other issues SKS has that you have to work around. 

This is not a SKS issue, SKS is working as designed.

Reply #10 from WinCustomize Forums Top

Well then Neil, if it's not an SKS issue, what is causing it then? 8|

Reply #11 from WinCustomize Forums Top

Quoting LightStar, reply 10
Well then Neil, if it's not an SKS issue, what is causing it then?

You are mistaking it for a problem when it is not.  SKS writing those values is working as designed.

Reply #12 from WinCustomize Forums Top

I think that there's no reason to bother with those files at all as this will not affect your final work and this will not matter to the users at all.

 

if you're still annoyed by that as you're designing a Windows7 only visual style, here is what I did (as I only design for Windows 7 for a while now)

 

Make your Windows 7 skin and then make and add some generic parts for the XP sections, with generic, I mean some design that would work well

with any kind of visual style.

 

Done, from now on, always use this visual style as base for your future works and only touch the Windows 7 parts.

 

With this method you will never have to bother with the XP parts but if a user still try to use your visual style on XP,

it will work as the parts are there.

 

Just a suggestion, of course :)