Author: messpert
[Added to the original trac issue at 1.54pm, Tuesday, 10th May 2011]

I should have added that the satnav has 3.5inch colour 320x240 TFT display touch panel,
and 64MB ram.

Author: messpert
[Added to the original trac issue at 4.32pm, Saturday, 14th May 2011]

I have now discovered that moving over to the far right of the search box works.
It seems that the "+" button overlays most of the search box, and adjusting the button size
as above does not help.

I will adjust the priority to minor, although until one discovers the way to get in,
it is still "critical" :-)

Author: messpert
[Added to the original trac issue at 8.18pm, Tuesday, 31st May 2011]

The problem is back, so I am restoring the priority to critical. I think that I accidentally
ran the old version when I reported that it worked again.

So this is a show stopper on Wince, at least on the version here.

Author: openstreetmap[at]rational.co.za
[Added to the original trac issue at 8.35am, Wednesday, 1st June 2011]

I've never seen the problem as you describe it.

I know that searching is a real pain on devices without soft keyboards. Then you need to set Keyboard=1 and that keyboard obscures search results and cannot be hidden. I'm attaching a patch made by burebista that alleviates it somewhat.

I don't think it worthwhile improving the WinCE port. Android devices are now cheaper, with better hardware (compass, accelerometers and GPU), more user friendly (esp. multitasking) and easier to program and debug.

Author: messpert
[Added to the original trac issue at 7.11pm, Wednesday, 1st June 2011]

It's a WinCE Core 5.0 if that makes any difference. And the previous
version of gosmore worked fine, so it must be a side effect of some
change?

This has a soft keyboard. I would expect it to work if I could activate
search. So far as I can determine, it is a simple matter of the button
not being accessible.

If I set Keyboard=1 on the previous version, then the keyboard
completely vanished.

I think that we may be at cross purposes here. Indeed, on the older
gosmore, the soft keyboard did restrict the number of search results
accessible. Changing the search spacing helped a bit.

But that is not this bug. This bug is the complete inability to
activate seacrh at all. Apparently no button at all. Surely it is
must be something trivial, easy to fix? At least to get back to
where the previous version was. I agree that sorting out the
search layout to avoid the keyboard obsuring results would be a
bit more of an effort.

Thanks for the reply and all the work.

I still think it is critical if not a blocker for those of us with wince sat navs.

Author: dmgroom
[Added to the original trac issue at 10.29am, Saturday, 13th April 2013]

Just in case anyone else is having the same problem, then try:

set Keyboard=1 ; then exit Gosmore ; then restart Gosmore