Needs to support all screen sizes

Bug #579431 reported by Kieran Fleming on 2009-10-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Guillaume Rosaire

Bug Description

Devices with different screen characteristics will be released soon and work needs to be done to signal if OSN is compatible with them.
Lots of info is here on how to do it is here:
Under the heading "Strategies for Legacy Applications" there are instructions on how to support these screens while retaining backwards compatibility.

I've quickly tested the program in all the 1.6 resolutions and everything seems to work with compatibility mode disabled but I'm not sure how readable the map will be on high-res, high dpi devices.

Guillaume Rosaire (zerog) wrote :

1st analysis :
- no AbsoluteLayout or px coordinates found in layouts.
- 2 solutions for imgs (i.e. icons) : let the device do the upscaling for icon.png or generate several different files and put them in drawable-nodpi, drawable-hdpi, ...
- deeper analysis needed for OpenStreetMapView which relies heavily on pixels transformation and coordinates to display the OSM tiles.

At the moment, Maps should be displayed correctly but upscaled. We need to refine the tiles display on big screen.

Will Uther (willu-mailinglists) wrote :

See also the patch for Issue #70.

Currently OSMView will load the tiles based on view size, and it looks (but I haven't tested) like it will correctly re-calculate everything. The issue I found is that there is only a fixed size in-memory tile cache. If that in-memory cache isn't large enough to hold all the tiles for one display then they'll get loaded into it one at a time. After each image is loaded the display is invalidated. This leads to a progressive display of the map, with old bits disappearing when the new bits are drawn. It constantly cycles.

The patch in issue #70 adds dynamic enlarging of the in-memory cache so that it can hold a complete display's tile set.

chris_debian (cjhandrew) wrote :

Pushed-back. Needs re-assessing in line with other issues after 0.9 release.


To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers