WinCustomize Forums
Having a small problem with windows and apps not opening fullscreen.
They will go fullscreen only if I restore them and max them again.
They dont use my frame cutoff settings til then.
WB7,XP,bitmap frames,latest nvidia drivers,8600gt. 
(animated frames)
Which apps?
You should know that frame cutoff settings do not apply to per pixel skins.
yes I know about perpixel frames...these are bitmap frames(the skin has no perpixel frames) I have set cutoff to match the way perpixel works.
which apps?...all apps that are skinned by WB.
thank you Neil.
Been having a similar problem here for ages I.R., but only with certain applications like Paint Shop Pro and a couple of others I cannot recall right now. But I am using per pixel frames. 
Same here.
My customary skin uses non-PP frames and, except for Windows Explorer (always has been the case), maxed windows would open full-screen & 'respect' the MaxBorderCut settings. I installed & applied Jakuta a couple of days ago which uses PP frames by default & ran into that bordercut issue immediately (as expected with PP frames). I went into WBConfig, checked 'Never use per pixel frames' & reloaded the skin but it still wouldn't respect the MaxBorderCut settings with Jakuta's non-PP frames. Reverted to my prior skin & the problem remains - every window set to open maxed opens with the 4px bordercut. It's as if loading that PP skin 'set' something that got 'stuck'. Guess we need Hillary's Reset Button.
Using current WB7 on XPP SP2.
well,for a switch I actually set the cut for the frames like Vista and 7 this time(rather than the way I used to do it so much or all of the frame would show)
I finally accept the microsoft way and it dosnt work 
Something definitely happened with the way WB handles those parameters between 7.0 Build 80 & 7.01 Build 83. I have 7.0/B80 running on two other rigs & it still respects/enforces/remembers the maxbordercut settings on those; 7.01/B83 on the one remaining rig (my daily user) does not.
Perhaps if we keep bumping this, Neil will take a look. 
He has...just waiting to see what he comes up with...he has many issues to deal with...doubt if this one is first...or even next. 
How could any of those be more important than this? 
Did you play for the 'Boys, BTW?
Updated to the 7.09 version today but doesn't seem to have fixed it. However, the About WB dialog says this:
Is this just the time-honored/traditional Stardock failed-to-update-version-info-with-app-update thing or did my install get borked? FWIW, it did hang for about a half hour at the 'verifying' stage & I had to cancel/restart the update.
I'm no expert on those file versions but that sure looks wrong.
Welcome Guest! Please take the time to register with us.
JoeUser Forums
