Small problem with skins

[DaveStall]

I have recently just started using Dashboard again since I got my new device (HP2210) and I am having a strange problem with skins. After I did a soft reset on my device, the bottom bar (the area with the "New" button) became "unskinned". That is, it is just the standard grey bar on the bottom as opposed to what the skin should be displaying. This is obviously a problem if the skin I am using has buttons (like the settings button) that get covered up by the bottom bar. I am sure I have done something stupid to create this problem, but I can't for the life of me figure out how to get this bar skinned again. I have tried reinstalling the skins, moving them, etc. The skins I am using were made for the mobile (2003) devices, so I don't think it is a skin compatibility issue (they did work at one time afterall). Any help would be appreciated.

Dave

[citats]

Originally posted by DaveStall
After I did a soft reset on my device, the bottom bar (the area with the "New" button) became "unskinned". That is, it is just the standard grey bar on the bottom as opposed to what the skin should be displaying. This is obviously a problem if the skin I am using has buttons (like the settings button) that get covered up by the bottom bar. I am sure I have done something stupid to create this problem, but I can't for the life of me figure out how to get this bar skinned again. I have tried reinstalling the skins, moving them, etc. The skins I am using were made for the mobile (2003) devices, so I don't think it is a skin compatibility issue (they did work at one time afterall). Any help would be appreciated.

Dave

Dashboard does not skin this bar. Dashboard only skins the today screen (desktop area)
wisbar advanced or ICbar both skin the command bar (bottom bar) So if you are using one of these programs look at the settings with in them. Or if your not using them you need to get one of them to skin the bar.

[DaveStall]

Thanks you very much citats. That certainly gives me something to look at. I am using Wisbar Advanced, so perhaps something got messed up there.

Dave