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?