There is something that bothers me about the Background Preference app. The scaling option for displaying the backgroung picture gives horrible result (going from 1024x768 to 1154x864). The old Background pref did this and the new one does the very same thing.
It’s not a very useful option when it ony produce such a miserable output. Is there a reason (using specific API) why this behaviour is still there and that it doesn’t properly resize(resample?) the pic?
Could it be the new NVIDIA drivers that do this? I don’t remember which supported card I had before the GF5200 and/or if it did the same behaviour. :x
There is something that bothers me about the Background Preference app. The scaling option for displaying the backgroung picture gives horrible result (going from 1024x768 to 1154x864). The old Background pref did this and the new one does the very same thing.
It’s not a very useful option when it ony produce such a miserable output. Is there a reason (using specific API) why this behaviour is still there and that it doesn’t properly resize(resample?) the pic?
Could it be the new NVIDIA drivers that do this? I don’t remember which supported card I had before the GF5200 and/or if it did the same behaviour. :x
Its the app_server. Not the prefs panel, not the graphics card. Just get a background that fits, all OS’s have resizing problems.
Just get a background that *fits*, all OS's have resizing problems.
That’s really not true, the 2 resolutions he is using are the same aspect ratio, granted you lose something anytime you enlarge something, but honestly going from 1024 to 1152 shouldnt cause much of a noticeable difference if the source image is fairly clear.
I guess Tracker could do some kind of bilinear resize on the image before it draws it - the BView->DrawBitmap API doesn’t do any complicated smoothing when it draws stuff at a different size, it would be too CPU intesive to do it every time.