Thanks again all for your very helpful suggestions. Turns out, I was at fault for claiming WinScreenMode returned 0 on the T3, I was accidentially using %d to display the value, which doesn't work with UInt32 (it prints out 0 regardless). Stupid mistake.
And as is often the case, the problem was elsewhere in the application. My problem was not realising WinScreenMode posts sysNotifyDisplayChangeEvent, which really messes things up when I do something specific under winDisplayChangedEvent. A flag fixed this. In the future I'll be sure to use PilRCExplorer, thanks for that tip. I have to add though that I find it a bit strange that the OS doesn't automatically set the best available bit depth (hence 8 bits are default on the T3 unless you do something active to change it). But there's probably some good reason for that too? -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
