Hi Nathan. New user and first post.

I think I may have found a little bug. The goto function seems to work perfectly when using "List" for all waypoints. But is unpredictable at times when using "List" for nearest waypoints.

From my experiments it seems to be when there are more than 10 waypoints and the selected waypoint is below the bottom of the first displayed page.

I would try to select a waypoint for "goto" and it might send me to a totally different waypoint or leave me on the last one selected for "goto" or send me to the correct one.

This is my best description but I'll be glad to try to answer any specifics if you can't recreate this.

Jim

Another note. You are probably already aware but thought I'd mention, "nearest places" acts the same way.

I'm guessing they use the same software functions, just different data sets.

My first observation of being related to page two is incorrect. It happens from page one also. Funny though, I could not get it to act up from the first five data entries.

I'm running 2.6.1


Jim

Post script:

Nathan, there is definitely a pattern. So that I could easily see what was going on I edited the 30 nearest waypoints and named them 1 thru 30. With 1 being closest, 30 being most distant.

Selected sequentially or randomly and asked to be centered, here is the result:

Selected  --  displayed

1  --- 1
2  --- 2
3  --- 3
4  --- 4
5  --- 5
6  --- 7
7  --- 6
8  --- 10
9  --- 8
10 --- 9
11 --- 12
12 --- 11
13 --- 13
14 --- 15
15 --- 14
16 --- 19
17 --- 23
18 --- 16
19 --- 17
20 --- 18
21 --- 20
22 --- 27
23 --- 28
24 --- 21
25 --- 22
26 --- 25
27 --- 24
28 --- 29
29 --- 30
30 --- 26

Sorry to report it is still not correct Nathan.

Updated to 2.6.2

Now, if it centers on the wrong waypoint, when I go back to the list and wait a few seconds the last previous waypoint that was actually centered becomes highlighted- even if it was not the item selected for centering. So the map and highlighted member of the list eventually match, but some selected items still are not properly centered.

And, I'm getting a "binding" error - Cannot bind to the property or column ID on the Datasource. Parameter name: dataMember. This did not occur in previous release.

Jim

I'm sorry this is so long and tedious, but I think all this information is necessary for proper
duplication of events.

Phone ATT 8525
SW Windows Mobile 6
BCN is installed in main memory
Map and waypoint file is on MicroSD
Map is Topo around Cedar City Utah, Approximately 30x30miles
Waypoints are from Geocaching.com, quantity 50 imported to BCN from GPX file
GPS is I_Blue737 attached via bluetooth

Gps is on, connected and 3D fix (tracked 8, fixed 7) at my home
While observing the behavior, I am stationary (GPS on the window sill)

GPS options are:
 Center GPS - No
 Keep on screen - No 

List Nearest Waypoints correctly sorts and displays by distance.

I'll only deal with the first dozen or so Waypoints

Waypoint  1 0.44mi
Waypoint  2 0.48mi
Waypoint  3 0.57mi
Waypoint  4 0.73mi
Waypoint  5 0.89mi
Waypoint  6 0.9mi
Waypoint  7 0.92mi
Waypoint  8 1.04mi
Waypoint  9 1.08mi
Waypoint 10 1.1mi
Waypoint 11 1.1mi
Waypoint 12 1.25mi
Waypoint 13 1.32mi


When these waypoints are selected sequentially (1 - 13) and asked to be centered, here is what happens.

Select Waypoint 1, press center  - map is displayed, centered on Waypoint 1
Go back to list, Waypoint 1 is highlighted
Select Waypoint 2, press center  - map is displayed, centered on Waypoint 2
Go back to list, Waypoint 2 is highlighted
Select Waypoint 3, press center  - map is displayed, centered on Waypoint 3
Go back to list, Waypoint 3 is highlighted
Select Waypoint 4, press center  - map is displayed, centered on Waypoint 4
Go back to list, Waypoint 4 is highlighted

So far so good.

Select Waypoint 5

Highlight of Waypoint 5 does not "stick".

Wait a few seconds, it highlights Waypoint 6, Wait a few
more seconds, it highlights Waypoint 7. It then cycles W5,W6,W7,W5,W6,W7... continuously.
This is with no operator intervention.

The waypoints in the list do not change position. It's just the highlighted row moves from
position 5-7 on the screen.

If I push the center button when Waypoint 5 is highlighted, the map is displayed, centered on Waypoint 7.

If I push the center button when Waypoint 6 is highlighted, the map is displayed, centered on Waypoint 5.

If I push the center button when Waypoint 7 is highlighted, the map is displayed, centered on Waypoint 6.

This is very repeatable.

Trying to select Waypoint 8 does not stick, it is similar to above except it goes W8,W9,W8,W9,W8,W9... continuously.

If I push the center button when Waypoint 8 is highlighted, the map is displayed, centered on Waypoint 9.

If I push the center button when Waypoint 9 is highlighted, the map is displayed, centered on Waypoint 8.

This is very repeatable.

Selecting Waypoint 10 works correctly. The highlighted row does not change, and Waypoint 10 is correctly displayed and centered.

Selecting Waypoint 11 works correctly. The highlighted row does not change, and Waypoint 11 is correctly displayed and centered.

Trying to select Waypoint 12 does not stick, it is similar to above except it goes W12,W13,W12,W13,W12,W13... continuously.

If I push the center button when Waypoint 12 is highlighted, the map is displayed, centered on Waypoint 13.

If I push the center button when Waypoint 13 is highlighted, the map is displayed, centered on Waypoint 12.

This is very repeatable.

I have not been able to duplicate the "binding" error tonight. If it happens again, I'll try to capture the events. But it was when doing things similar to the actions noted in this post.

Best of luck

I've changed some things for nearest waypoints and places in 2.6.3. I won't know if it will help you until you try it. It may not fix the Data binding error because I still haven't seen that. 

If you see the datamember error, does it bring down the program? Is there a chance to look at "Details..." and see a stack trace?

Thanks for your efforts Nathan. So far so good with 2.6.3. Whichever nearest waypoint is highlighted winds up centered when requested. I think that issue is resolved for me. I'll keep you posted if it rears its ugly head again.

I do still see the anomaly of the highlighted row in nearest waypoints changing on its own.

I tried to recreate the binding error like before, and so far, no problems there either.

Now I just need to get out and try it in the real world.

Jim