Opened 9 years ago

Last modified 8 years ago

#3415 new defect

Gosmore on Windows CE/Mobile: Shows too few search results

Reported by: messpert Owned by: nroets@…
Priority: major Milestone:
Component: gosmore Version:
Keywords: Cc:

Description

Non trivial routing with gosmore on wince (tested on WinCE 5.0) is almost impossible because scrolling is not implemented.

The natural way to set an end point is to use the search box. On a small screen, typically only 3 entries are shown, the lower half of the screen being covered by the virtual keyboard. There seems to be no way to scroll down to find more distant places.

Trying to zoom out on the main map to manually centre on a distant end point is pretty hopeless, since gosmore becomes impossibly slow at low zoom ratios.

This coupled with the fact that gosmore then typically loses the end point when the zoom level is changed (etc) mentioned in another ticket means that it cannot be used for more than very local routing on portable devices. At least while they are running wince.

Change History (2)

comment:1 Changed 9 years ago by openstreetmap@…

Summary: Gosmore on Windows CE/Mobile: user interface prevents routingGosmore on Windows CE/Mobile: Shows too few search results

On devices with Sip and Common Controls you can set Keyboard to '1'. The resultant Sip keyboard is typically smaller and can be dragged around, allowing you to access more of the search results.

comment:2 Changed 8 years ago by messpert

Setting keyboard to '1' on my satnav seems to disable search completely. The problem remains on the latest 2011 version of gosmore.

Note: See TracTickets for help on using tickets.