Still having MAJOR skin update/delete issues.

Ancient problem...still a huge hassle.

from WinCustomize Forums
This has been brought up many times and nothing ever done about it.  

vStyler and I send skin updates regularly to each other and other testers...we even delete our own skins if there is a need to and reinstall backup versions.

We send updates to customers.We ALWAYS tell them...dont forget to uninstall old version before installing new.(many will neglect to do this,we sometimes forget and we are right in the damn middle of discussing it  )

But a simple 'delete this skin' from wbconfig isnt enough...more often than not,it leaves the folder either empty,or with 1 or 2 fonts in it.(sometimes not being used by the current skin so it aint that)

Attempting to install the skin,WB renames it and no skin shows in the skin list.Sometimes it hangs so bad while attempting to install,you have to reboot...to a blank skin...if your lucky.

So you go into WB folder and attempt a manual deletion...werks sometimes,others REFUSE to delete...so now you cant get the update to install at all without a reboot.(one folder was completely empty...and would NOT delete)

We have come to the conclusion that we should NEVER update a skin because half of the people will see no difference or it will even hang their pc.

Unfortunately,skinners dont have the option to NOT update while creating...its part of the process.  
windowblinds
10,106 views 40 replies
Reply #1 from WinCustomize Forums Top
In short.. with no rhyme or reason.. WB is (sometimes, more often than not) leaving empty (except for a font or two) , undeleteable folders in the WB directory. THE only way to delete it is to reboot first. Unloading WB does not help, nor does killing explorer.

Because the skin is not completely deleted , many times when trying to update it after "deleting" It does not not update correctly and in some cases causes bizzare anomalies in the skin.

Say's its deleted...its not....completely.

After almost a week back and forth exploring this ..we gave up. I personally, until something can be done about it will not update any skins for any reason.

This has been brought up before to no avail. We thought we would give it another shot.

The first function of a skinning engine IMO..before anything else should be to seamlessly transition from one theme to another, whether updating or installing.

P L E A S E advise. It's personally killing me.  
Reply #2 from Stardock Forums Top
Guys - sounds like you're looking for feedback from other skinners. As a user, I have WB set to not use the skin's icon nor wallpaper. I make those changes manually. Those are two less things to worry about during a skin delete.

After I delete a skin the first thing I do is go to the Windowblinds folder and delete the skin's folder if it's still there. If I can't delete it, it's usually because the skin installed some fonts at the OS level. I re-boot and then delete the fonts and folder. I assume at that point the skin is fully deleted. Are you saying that from your skin update experience that the skin is not fully uninstalled at that point? I can't find traces of the old skin in the modified files (e.g. skins.nbd or the in the registry). I assumed it was now gone and it could be updated.

Thanks,

Sleep
Groupy 2 - Organize multiple applications into grouped tabs on your Windows desktop
Reply #3 from WinCustomize Forums Top

The problem MeSleeper.. IS the reboot. After a reboot there is nothing, correct. That is the whole point. A skin should NOT be leaving fonts somehow in use and undeletable after deleting the skin from WBconfig. Even after an Unload or an Explorer kill. The folder \fonts are access denied.

The entire contents of the folder and the folder itself should be GONE...without.. a reboot OR it should be common knowledge that a reboot is required.
Reply #4 from WinCustomize Forums Top
You two are certainly the most rambunctious skinners I ever saw. Just reboot and delete the whole folder with fonts is that very difficulty?? I don’t think so.   
Reply #5 from WinCustomize Forums Top
Even after a reboot...the skins folder was STILL there...at that point it finally was deletable.  

How can you expect the average user to go thru all that?We dont have time for all those shennanigans...stop what your doing...reboot...finish deleting...just to test a damn skin update.    
Reply #6 from WinCustomize Forums Top
Shut up Nicholasworld...Yes,it IS too much trouble to do...especially while werking.  
Reply #7 from WinCustomize Forums Top
Pretend your a skinner for a sec...Kitty sends me an update to test...John sends me an update,Basj sends me an update...etc...get the picture doofus?  
Reply #8 from WinCustomize Forums Top
Fact is when consulting with several skinners updating each others skins on eaches machines frequently then YES..rebooting gets REAL old REAL fast..Also, I don't remember stardock ever mentioning that a reboot was required to remove a skin.

NicholaSSworld take your insults elsewhere please, no one is interested in what you have to say. You contribute nothing here but insults and inuendo. A waste..frankly im getting REAL sick of it. You contribute N O T H IN G.   
Reply #9 from Stardock Forums Top
Guys - isn't the font load a Windows issue? Doesn't Windows manage the fonts? The only way to delete them is to unload them from Windows (which is what re-boot does).

Have you asked Stardock directly to see if they could add a warning box after a skin delete? Surely a check could be made to see if the folder has been fully deleted. If it hasn't, a warning box could pop-up instructing the user to re-boot and manually delete the folder. Perhaps that's the whole point of your post

Sleep



Reply #10 from WinCustomize Forums Top
That would be something at least for the end user... 

But dosnt do diddly for the skinner.   
Reply #11 from WinCustomize Forums Top
Pretend your a skinner for a sec...Kitty sends me an update to test...John sends me an update,Basj sends me an update...etc...


So?? Just deleted and rebooted should still have residues out there.


rebooting gets REAL old REAL fast..Also, I don't remember stardock ever mentioning that a reboot was required to remove a skin.


It’s font matter of setting by Windowblinds on system. Unless Neil has considering tackling this issue in future update, it didn’t affect Windowblinds functionality on user.

Reply #12 from WinCustomize Forums Top
Guys - isn't the font load a Windows issue? Doesn't Windows manage the fonts? The only way to delete them is to unload them from Windows (which is what re-boot does).


Sometimes the folder and fonts in question havnt even been used...so windows NEVER loaded them.Only WB is holding them for some reason...I've had EMPTY skin folders that wouldnt delete...no hidden files...NOTHING.  
Reply #13 from WinCustomize Forums Top
It’s font matter of setting by Windowblinds on system. Unless Neil has considering tackling this issue in future update, it didn’t affect Windowblinds functionality on user.


WRONG  Wouldnt delete fonts NOT BEING USED.NOT LOADED IN MONTHS.SKINS THAT HAD NOT BEEN APPLIED IN MONTHS!So STFU you ignorant moron.  
Reply #14 from WinCustomize Forums Top
Perhaps that's the whole point of your post


Yea.. that and not having to reboot to delete a font that is no longer being used ANYwhere.
Reply #15 from WinCustomize Forums Top
Sometimes the folder and fonts in question havnt even been used...so windows NEVER loaded them.



Nope,it still in use,you have to reboot to get release of some fonts seeting on system.
Reply #16 from WinCustomize Forums Top
I quit disucussing. I wonder Administrator should take concern on scurrilous comments as I keep seeing it.
Reply #17 from WinCustomize Forums Top
Nope,it still in use,you have to reboot to get release of some fonts seeting on system.


You dont get it stupid...Sometimes even skins that were not applied for months...fonts that were not used for months.    
Reply #18 from WinCustomize Forums Top
get the picture doofus?


you never fail to crack me up, Michael.   


I don't pretend to know all about it but it seems as if the font shouldn't have to be an issue. If I'm correct, the Xion skin format, for example, loads fonts contained in the skin file dynamically; deleting the skin causes no similar issues such as IR and vStyler describe.

Seems as if WB could be made to do the same. It sure would be a lot more user .. er, skinner friendly.

Reply #19 from WinCustomize Forums Top
Fonts not even installed.GO AWAY Nicholas.
Reply #20 from WinCustomize Forums Top
Let me clarify a little.. If my skin uses Calibri and I delete the skin from WB.. then Calibri should be deletable from the WB directory when I unload WB and am using LUNA.. which does not use Calibri. Yet the font remains undletable until after a reboot. Its very simple.

and Nick.. if you continue to insult people and no one does anything about it on our behalf.. we will resort to lowering ourselves to your level. I have asked you repeatedly to stop following me around, insulting me and causing trouble, yet you continue to do so.

So.. I will echo my colleague's sentiments.. stfu.
Reply #21 from WinCustomize Forums Top
I don't pretend to know all about it but it seems as if the font shouldn't have to be an issue. If I'm correct, the Xion skin format, for example, loads fonts contained in the skin file dynamically; deleting the skin causes no similar issues such as IR and vStyler describe.


How astute of you Stephen...somebody gets it.  
Reply #22 from WinCustomize Forums Top
astute ... hmm ... astute .. yes! .. I'm astute!


had to think about that one for a minute.     
Reply #23 from WinCustomize Forums Top
Don't know if this might help you guys, but I use a program called Unlocker that might work for you.

Unlocker

It has worked for me in similar situations. Just a thought.
Reply #24 from WinCustomize Forums Top
might at least speedup the process for skinning purposes.

Dosnt help with end user issues tho.

Thanks bobdown