I recently tested with a template, and there are two ‘bugs’ that I think I found, but it’s strange nobody reported…

I recently tested with a template, and there are two ‘bugs’ that I think I found, but it’s strange nobody reported them before, so maybe there are not.

I exported a template from a nexus 4, and imported it on a galaxy tab. The screen resolution is very different and:

1) the template had a panel with a grid of: columns-fixed number-1, rows-fixed size-79. When I imported it, after the scaling lightning does, the panel still had columns-fixed number-1 (which is expected and right) but still rows-fixed size-79, which is not because this way if the screen is shorter less items are shown and vice versa.

2) the template had the desktop set to ‘portrait only’ but when I imported it the tablet was in landscape and after the importing it changed to portrait. I then realized that all items were wrong placed, and when I changed the setting and rotated it to landscape, it was ok. I guess that in the import screen the orientation matters, so maybe you may add a check of the template final orientation, or even a pop-up to let the user choose it (the final orientation) before apply.

And last, but maybe this is not so important, what about a setting to disable the scaling? When creating it, or when applying it. Maybe a screen is made to automatically adapt, and the scaling broke some configs (not sure about this last one suggestion, anyway I guess a backup does the trick, not tested)

]]>

2 Commentsto I recently tested with a template, and there are two ‘bugs’ that I think I found, but it’s strange nobody reported…

  1. Anonymous says:

    < ![CDATA[

    Indeed, I probably forgot to add some scaling for the grid size. This might not be the only setting like this 🙁


    Regarding the orientation, I must admit that I prefer to leave it unchanged: the reason is that I am unsure how it will behave in practice. The orientation might be more a user preference than a device specific thing. For instance the N7 “natural” orientation is portrait, but you may prefer to use it in landscape. So yes, a checkbox would be a better way to handle this than an automated translation.


    I would say that a setup that automatically adapts to the screen can only be made with scripts (or grids), so maybe that scaling or no scaling does not make any difference because coordinates will be overwritten with computed values anyway ?

    ]]>

  2. Anonymous says:

    < ![CDATA[

    Orientation-bug I did notice and must, as Pierre Hébert says, be handeled with care. My Android-box is convinced that my TV is portrait. 😉

    ]]>

Leave a Reply

Your email address will not be published. Required fields are marked *