View Single Post
Old 11-30-2010, 12:35 PM   #51
kartu
PRS+ author
kartu ought to be getting tired of karma fortunes by now.kartu ought to be getting tired of karma fortunes by now.kartu ought to be getting tired of karma fortunes by now.kartu ought to be getting tired of karma fortunes by now.kartu ought to be getting tired of karma fortunes by now.kartu ought to be getting tired of karma fortunes by now.kartu ought to be getting tired of karma fortunes by now.kartu ought to be getting tired of karma fortunes by now.kartu ought to be getting tired of karma fortunes by now.kartu ought to be getting tired of karma fortunes by now.kartu ought to be getting tired of karma fortunes by now.
 
Posts: 1,637
Karma: 2446233
Join Date: Dec 2007
Device: Sony PRS-300, 505, 600, 650, 950
Mark, code could check for model in:

Core.config.model

or:

System.applyEnvironment("[prspModel]")

It would be cleaner, however, to check for something like "hasTouchScreen". I'll add it to "compat", it will be defined and set to true only for models with touchscreen. So:

Core.config.compat.hasTouchScreen

PS
Just came to my mind, that "hasNumericButtons" is already there and could be used instead of "hasTouchScreen" with negation.


Long story short: Core.config.compat.hasNumericButtons is set to true on 505/300, and will be set to false on all touch devices.
I doubt we'd ever see reader with numeric buttons and a touchscreen.

Last edited by kartu; 11-30-2010 at 12:38 PM.
kartu is offline   Reply With Quote