03-31-2011 01:50 AM
yesterday i discovered that including cacheAsBitmapMatrix in code being debugged on the PlayBook simulator will greatly distort display objects assigning that property.
i just discovered that including NativeWindow.isSupported (which can be used to determine the current device profile) in code being debugged on the simulator also causes graphical errors – in this case the entire stage is squeezed slightly thinner. very strange effect.
i realize the Simulator is currently a beta, but since both cacheAsBitmapMatrix and NativeWindow.isSupported poll for a desktop vs. mobile device profile of the application i'm concerned that these (and perhaps a few other) properties can never function correctly as intended on the simulator.
both cacheAsBitmapMatrix andNativeWindow.isSupported are essential in maintaining a single code base for multiple desktop and mobile deployment targets.