The problem with states and skinstates is that they are single use. I'm
adapting a desktop app to mobile and I want to support portrait and
landscape views. According to a couple of pages on the net you should
create a portrait skin state and a landscape skin state.
Sounds good, but I am already using my skin states for something else, some
real lifecycle states of this component like active, inactive,
expired, etc. I'm not going to multiply all my states and create
activeportrait, expiredportrait - sounds like code bloat to me.
Anyone else encounter this kind of problem and can point me to the best way
forward?
John
