WB6 changes without apply still keeps the changes

If you go into WB6 and let's say just go into Coloring and put a check in, but don't click on Apply Changes but instead close the program with the X, the checkmark choices are still kept. This is nasty because if you make a change you don't want to keep the easiest way in "All Window's History of Programs Every Made" a simple Cancel or in this case a close of the program prior to clicking OK or Apply would revert the changes back. Why doesn't WB6 behave this same way? It gets really anoying when you're just messing with choices and clicking in checkmarks just to see what the submenues on enable are, but don't want to keep those settings. Instead of just being able to click close and have it not keep the settings, the damn thing keeps them, so you have to go back and undo all the work you just did and hope you remember what you changed or didn't change. Bad design choice guys... can this be changed to better match what the normal process functions in Windows should be? WB6 should not save the setting changes with every single damn click you make in the program. You get what I'm trying to say?
2,771 views 6 replies
Reply #1 Top
Changes on the fly, it's the "new way" Can't say I care for it either, should be optional, but once your competent, you'll be ok.
Reply #2 Top

Yes.  Though I don't agree.

If I want to change the color of my skins, I click a checkbox to do it. I don't expect to have to press some save button.

Reply #3 Top
I agree with that Brad but for new skinners in an app made to accommodate said skinners I can imagine it may be disconcerting. Would it be difficult to have an option to bypass this? Personally if I could, I would. What's one more click ? Also it strains the processor to constantly update, many times one may want to make several adjustment's without applying first.

I'll live either way, I'm pretty much exclusively using 5 + code tab still anyway until Vista is sorted out.
Reply #4 Top
vStyler : I think this thread is about wbconfig rather than SKS.
Reply #5 Top
I think this thread is about wbconfig rather than SKS.


SKS 6 does this too doesn't it? Honestly I apply changes everytime regardless and I work very quickly so I don't really notice but I was led to believe that SKS6 final would apply on the fly, am i wrong about that?
Reply #6 Top
Yeah, my post was about wbconfig. It's kind of anoying that it applies on the fly for choices like that, but the skinning apply does not. It messes with me and I'm sure others as well. How hard would it be to keep it from doing the "on the fly" option changes?