window resizing

W

wnowak1

Registered
Will anything be made to the way windows are resized in OS X? It is absolutely horrible. Its not smooth at all. Compared to windows XP or 2k. Resizing windows in MS is smooth and continuous. On OS X it jerks and you to pause for it to update to see where the position of the window is...If you don't like it, you have to continue resizing it. Its a tedious process.

Will panther have a solution for this? Is there a way to have outlined window resizing (opaque?) ?

For the curious, I have two macs. The new powerbook 12" 1, ghz, nvidia fx
and a dual 1 ghz radeon. Both resize windows at a slow, jerky, fasion.

Thanks
 
HMM...strange on the new powerbook. what build of panther are you using? did you upgrade to it. 10.3 7b74 is smooth when it comes to all window resizing on my 1.6 G5. Perhaps a clean install would help. Just my 2 cents.
 
resizing windows was horrible since os x came out.

I thought by now they would have an option to make it either smooth like in windows xp or outlined resizing.
 
Window resizing is much more advanced in OS X. The way Windows does it is quite smooth, this is true, but they often have redraw glitches that can make it look very ugly. You won't see these in OS X, but the technology behind this also contributes to the tardiness of resizing windows. It's really something you'll have to live with.

You could try optimizing your OS a bit. For an explanation of how to enable window buffering, look at the last post in the thread "Mac faster than PC?" on this site. It should be mine.
 
How fast does it update? I don't have a single app where the resize doesn't happen at LEAST 4-5 frames per second, and my system's not much faster than yours.

The answer to your question though, is no. There's nothing you can do (unless your system is extraordinarily slow for some reason)
 
On the recent computers I've used (my dad's dual 1.25 Ghz G4, G4's and G5's at the stores), windows resize really smoothly, so I don't know why you're having trouble with a 1 Ghz machine.

Maybe reinstall the OS? No, don't do that...
 
From what I've noticed, the size at which the window resizes is directly proportional to the size of the window.

Finder windows on my system resize faster and smoother when they're small; slower and more jerky when they're large. Same goes for Safari. I'm guessing it'd be the same for just about any app, since window resizing uses the same system calls for most of the apps out there.
 
That's a good point - I tend to run my screen at 1024x768, so my windows tend to be smaller than if I ran at, say, 1600x1200. If I run in that mode and expand windows all the way, they do resize quite a bit slower (2-3 frames per second instead of 4-6, at the least)
 
In my opinion, resizing is poor in Win XP and Win 2000.
The reason: the content doesn't follow with the resizing.
In safari it crunches together.

Another thing:
Thank the developer's of mac os x that safari doesn't do what IE does when you drag it. Makes multiple image layers on top of itself. Or launch 23-35 windows if it can't connect online to find Help.
 
I would have to agree, windows looks like garbage when you resize. Things start shifting out of place then they have to refresh to see things all lined up. And this was on a new machine. I won't bother touching this again, seems like my experience on a PC is always negative.
 
Okay, to sum it up: No, nothing will be done to solve this anytime soon. Ever faster machines will see less of a problem, but the basis for it is that Mac OS X doublebuffers every window in the GUI anyway, which results in some lag. My guess is that we'll see "something totally different" in the way Mac OS X handles windows maybe in 10.5 (2005) or 11.0 (whatever it will be called, maybe five to seven years away from now). For now, if resizing windows is something you do more often than actual work, you can switch to Windows. ;-)
 
Well, double buffering should make it draw faster. The way it works is you have a screen buffer which holds what is being displayed, and a background buffer which the computer draws to. When the back buffer is finished being drawn, the computer swaps the buffers. This is a lot faster than drawing to the screen buffer because IO to the screen is slow. It's much faster to flush a buffer to the screen with everything drawn than to draw each thing and have each change flushed to the screen as it's drawn.
 
I'm thinking the double-buffering doesn't so much provide speed improvements as crispness of updates and lack of the silly half-drawn stuff you see in Windows constantly...
 
Well, it does that as well because you won't see it drawing everything. But it also makes it faster. I've written OpenGL and DirectX programs and if you don't use double buffering, you will have a really slow program because you are drawing to the buffer that is being displayed, which is really slow.
 
You must log in or register to reply here.
Back
Top