HELP! Anyone!?

This is driving me nutz!

I can't, for the life of me, figure out what change I made that would cause windows that are minimized to go to the system tray. This began after applying a test skin I am working on. I have checked all the normal settings in SkinStudio and my other desktop enhancements, but can't remember any references to this kind of setting in Windows itself. Any help would be greatly appreciated.
42,761 views 11 replies
Reply #1 Top
First thing I always try is a re-boot, always amazes me what that fixes.
Robert
Reply #2 Top
I do believe there is a function in WB for doing just that - a button on the titlebar can be configured that way if I remember correctly. Perhaps you inadvertantly implemented that. I'm not really a WB skinner, so maybe someone with more experience will chime in...
Reply #3 Top
Is this happening with all skins or only your test skin?

I have checked all the normal settings in SkinStudio and my other desktop enhancements,


Check these two setting again..just to be sure.

1. In WB config dialog----->user overides--------->make minimize button minimize to tray. make sure that is not checked
2. In skin studio--------->minimize button------>action on click. Make sure minimize to systray is not selected
Reply #4 Top
Look in WB config > User Overrides > Advanced Settings box (top right quadrant) > see if the "Make minimize button minimize to tray" option is selected.
Reply #5 Top

top right quadrant

That would be "top left quadrant"....oops.

Reply #6 Top
Too slowwwww...............
Reply #7 Top
Is this happening with all skins or only your test skin?


No, all skins including Classic and XP Style.
1. In WB config dialog----->user overides--------->make minimize button minimize to tray. make sure that is not checked


First place I checked...I have this on double-click=Maximize and right click=send to bottom, so as NOT to interfere with the usual skin settings.
First thing I always try is a re-boot


Me too. And I have had to reinstall WB for a completely "my fault" reason...deleted skin inadvertantly in explorer instead of WBConfig.

These are the usual places to look when you skin...so I had to ask if anyone knows of an alternative or standard Windows setting that I am not bringing to mind.
Reply #8 Top

To the best of my knowledge, there is no native option in Windows to enable this behavior.

No, all skins including Classic and XP Style.

Does this mean that if you "unload WB > use Display Properties\Themes tab\Theme drop-down list" to apply the Windows XP theme that you see this behavior? Or is it only when WB is loaded?

Reply #9 Top
No, actually. It is a problem with WB. I have been trying all evening to do an uninstall to fix several problems that have started.

1. MDI buttons are not apparent.
2. Minimize button sends window to tray.
3. After first uninstall, WBConfig does not see any skins except Windows Classic, XP Style and the one I have current. The one I have current is only because I went through SkinStudio to apply, since SkinStudio can still see them all.
Reply #10 Top
Does this mean that if you "unload WB > use Display Properties\Themes tab\Theme drop-down list" to apply the Windows XP theme that you see this behavior? Or is it only when WB is loaded?


This has never been an option for me, I have always had to change skins with WBConfig.
Reply #11 Top

After first uninstall, WBConfig does not see any skins except Windows Classic, XP Style and the one I have current. The one I have current is only because I went through SkinStudio to apply, since SkinStudio can still see them all.

If WB still does not see the skins, I would venture to say this is part of the problem. It is my understanding that Stardock will attempt to release a new beta version sometime today 11/15, so you may want to restore Windows to the default theme > save skin folders > unistall / reboot / reinstall both WB and SS.

This has never been an option for me, I have always had to change skins with WBConfig.

I was referring to just the native "themes" engine and applying "Luna" to make sure WB is unloaded and see if the issue persists. Sounds like you already know it is somewhere in the WB application procedure - which makes sense.