Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Leopard resolution independence!!
- Thread starter zoran
- Start date
- Sort by reaction score
Plz explain further the [scaling factor to anything other than "1"] part that u said. What are the practical concequences of this? Im thinking of buying the 17" HDef MBPro and since Leopard isnt out yet and things arent so sure of the resol. indep. feature im afraid im ight be stuck with the HDef display and squint to see!!!! What do u advise me?
if you install the developer tools, there's an app called Quartz Debug you can use to test resolution independence out on 10.4.x. Not perfect nor complete, but you can still see what it does for yourself.
I dont have any access to the developers tools nor do i have the 17" MBPro with the optional display... i think im at a noway out here! And i cant decide if purchasing the MBPro wih the optional display will either harm me or help me!!!!
dev tools are a free download. however if you don't have one..
sorry, but can't help you there. for me there's an obvious answer to the mbp question, but I don't know you.
i still dont get the sarcasm
Lots of intelligent people don't, it doesn't mean you're not smart.
<been waiting for an opportunity to say that.>
Resolution scaling for the USER (not just the developer) has not been confirmed anywhere I recall, in Leopard... So where did you get that information? None of the developers posting about their Leopard experiences here have been talking about any scale settings in the System Prefs or anything either...
Exactly. Resolution independance support is mostly aimed at developers. Apple wants us ready for when they flip the switch and start scaling the interface, which I personally don't think will be 10.5.0.
The thing is, while people have been speculating left and right on what this will do for us, nobody has any solid information. We know what it /can/ do, but we have ZERO idea of what Apple wants to make it do in the future.
Not very likely to appear in 10.5.0, seriously. The resolution independence work is a bit like telling people their drivers need to be 64-bit clean a couple years ahead of schedule, and making sure they can do it. Apple will make the scaling available to the user when they feel apps are ready.
Damn! Even in their own iLife?
Although there are some options for increasing text size around in those apps, they certainly do not affect all text...
Resolution Independence is an OS-level function. Scaling the UI doesn't happen at the application level. The OS tells the app what scaling factor to use, and the app uses it. So if the OS says to use a factor of '1', no scaling is done in /any/ app. Some apps will be ready without any changes, but Apple still needs to turn the whole system on by wiring up something to the scaling factor. That hasn't been done.
That blurry raster image is from the LCD, and while resolution independence would help... it isn't what it is being used for. Apple has made it clear what the intent of the feature is for (ensure a consistent DPI as displays get more dense), but has not said anything about how/when it will be an active feature outside of some developer tools.
The goal is to have high resolution displays and make the OS the same physical size no matter what pixel density the display has, correct? Like some displays show OS X elements a lot smaller (for example the 17" MacBook Pro) than other displays such as lower resolution 23" Display that has a crappy resolution of 1680 x 1050... the OS UI elements would be a lot larger. I like the size of the UI on Apple Cinema Display 20"... it's a comfortable size for me.... but, with Resolution Independence coming, it could be this size on any display.
Not even that, resolution independence has /zero/ impact on the end user right now. For now, it is there for developers to prepare for, not for users to consume.
please enlighten me! but also tell me why!
personal preference - i love high resolutions.
try +option+8, along with the + and - keys. and check out the other accessibility options in system prefs.