Keeping Page Coloration Settings Through Restarts

You'll have to edit the skin to make the change permanent. Otherwise your changes will be reset everytime the skin is loaded.

Is that a hard thing to do, requiring a special application or is it akin to editing the Windows registry? If it's reasonbaly simple, do you have a link where the procedure is explained?

It's pretty easy with SkinStudio.

Are you using WB5?
Are you an Object Desktop subscriber?

I ask because I know of one case where simply opening a WB5 skin in the current non-Object Desktop release of SkinStudio caused problems with the skins.

I'm licensed to use WB5, and I am currently using it. I am not a subscriber to Object Desktop; I don't have skin studio.

Thanks for your help, but this becomes too complicated. I'll just have to reset it each time I restart, or perhaps just this as an opportunity to get acquainted with macro programs. I would guess it's easy to define a macro that would reset certain controls each restart.

On the other hand, I find that a competing product, of which I am also the licensed user,does not interfere with my settings. So in the interest of simplification, I might have to take the decision to use an otherwise inferior product--the competing one, that is.

I guess there's good reason why WB5 doesn't provide the option to retain these settings?

My bad. I assumed that Skin Studio was an expensive designer's suite. A post in another forum alerted me to the fact that certain changes one could make in the free program actually are as simple as changing the registry. I'm not that cheap or anything; I just didn't really want to spend a couple hundred dollars and learn a new program in order to change a single skin' page coloration.

Could you answer two more questions? 1) To change the page coloration in a skin as simply as possible, should I get the enhanced version with its "advanced skin colorizing," or do I need only the free version? 2) Is there a link to somewhere that tells me how to do it or is it explained in the program?

1) The free version will work just fine. It's a simple color setting. But, you really need to wait until version 5 is released. I've read more than report of SkS 4.6 breaking WB5 skins.

2) You can change the Windows background color by simply opening the skin in SkS, click the Classic Colors link (center panel), click the the preview to open the attributes in the right panel, select Window > Background - Window, set the color, and save.

I guess I'm a gambler; I took the "risk." Actually, I had intended to alter only a single not WB5-compatible single skin, and it wasn't a WB 5 one--bearing as it did a copyright date 2003. The best year for skins!

But once I got into it, I modified others, for one other element besides page color. Someone just reported you could resolve an incompatibility with the free form datbase UltraRecall (Kinook Software) by means of a small excision from the offending schemes.

Making these two changes in a variety of WB 5-compatbile styles had no adverse consequences.

If I may digress a bit, the excised element was "Windows tree expander" a small bitmap for customizing trees. The developer has now reported the problem to Stardock, but Stardock does not appear responsive.

This would seem to be a problem on the WB side, because the expander is a standard Windows component. Or if the compatibility is not Stardock's fault, the argument needs to be made to the supplier of the tree component.

the argument needs to be made to the supplier of the tree component.

This statement, at first glance, made me LMAO!! I then HAD to read the rest of the thread. Still funny...I am glad you got your thingy fixed.

srdiamond: We are aware of a report of a problem with a tree control and its on the list to be investigated. 

I suspect the problem is a flaw in how the control decides on the size of the expander buttons.  The size of those controls are fixed, but some skins do sometimes include larger images which are resized down during painting.  If the control were to size itself based on the size of that image then it would be doing so incorrectly.

Neil,

You did a great job of correcting this problem. But I would be interested in knowing whether the issue resided in WB or in the tree component. In other words, did you correct a mistake in WB, or did you compensate for a mistake in UR?