I have a similar use case as described in these topics Mapp View Screen testing and Mapp View multiple displays. Basically I’m developing a mappView visualization which will run on a 7" display, or optional 10" display.
I’ve started to create the 7" visu at first and just scale it for the optional 10" display by setting the mappView configuration attribute “zoom” to TRUE. This works quite good so far and all graphical elements are scalled up.
For the 7" variant, I’ve also created a custom alphanumerical keyboard. But when running the visualization on the 10", the keyboard does not scale and remains in the size of the 7" variant. See pictures below.
It’s not solved right now and I couldn’t find a workaround yet.
In order to keep the programming and configuration as low as possible, I’m only actively working on the 7" mappView files and for the 10" configuration I’m just referencing to the 7" mappView, like that:
With the “zoom” attribute in the mappView .vis-file, this approach works quite good for all graphical elements, only the keyboard does not scale.
In the 7" mappView visualization (.vis) I’m using my custom alphapad:
It would work if I would create a seperate mappView visualization for the 10" (and not referencing to the 7" file) and there put a 10" keyboard to the “AlphanumericKeyboard” attribute. But this has two disadvantages:
New 10" alphapad needs to be created
When adding new pages, bindings, etc. I need to update both mappView visualizations (7" and 10") so the changes are active for both. In the current project status, where a lot of changes are made, this would be a lot of work. The maintenance after project finish would be also more work and can be easy forgotten to update all made changes.
I agree with you, but at the moment I see that as a only solution, so I marked your reply. But I do not want to close discussion with that, so if enough can see better solution, feel free to add his comment as well.
