Alex Rieger

Recompiled with '-O0 -g' and got values. The open loop method (v1.6.2) was never going to converge with the values I saw. I tried compiliing the latest code snapshot straight out and had compiler errors. I copied the vikviewport.? from the snapshot and it had unresolved symbols. So I just edited in the change for that "Clip improvements, previous code was not working correct for long distances." issue link you gave for changes to vikviewport.c and compiled an it works a lot better. Must say that...

Recompiled with '-O0 -g' and got values. The open loop method (v2.6.2) was never going to converge with the values I saw. I tried compiliing the latest code snapshot straight out and had compiler errors. I copied the vikviewport.? from the snapshot and it had unresolved symbols. So I just edited in the change for that "Clip improvements, previous code was not working correct for long distances." issue link you gave in vikviewport.c and compiled an it works. Must say that a closed loop calculation...

Attached test1.vik - I can zoom to 2 pixelfact then it locks goig in straight from opening it. (The track lines don't always disappear prior to lock up.) Will set up to compile it local...

Attached test1.vik - I can zoom to 2 pixelfact then it locks goig in straight from opening it. (The track lines don't always disappear prior to locj up.) Will set up to compile it local...

I'm not sure what the 'optimized out' means. '(gdb) bt ' #0 0x0457ad2 in clip_x (y2=<optimized out="">, x2=<optimized out="">, y1=<optimized out="">, x1=<optimized out="">) at vikviewport.c:1264 '#1 0x0457ad2 in a_viewport_clip_line (x1=x1@entry=0x7fd8fc, y1=y1@entry=0x7fd8f8, x2=x2@entry=0x7fd8f4, y2=y2@entry=0x7fd8f0) at vikviewport.c:1300 '#2 0x0457b9d in vik_viewport_draw_line (vvp=<optimized out="">, gc=0xd1c6d0, x1=-159548, y1=19372, x2=-159549, y2=19373) at vikviewport.c:1314 '#3 0x043644c...

I'm not sure what the 'optimized out' means. (gdb) bt '#0 0x0457ad2 in clip_x (y2=<optimized out="">, x2=<optimized out="">, y1=<optimized out="">, x1=<optimized out="">) at vikviewport.c:1264 1 0x0457ad2 in a_viewport_clip_line (x1=x1@entry=0x7fd8fc, y1=y1@entry=0x7fd8f8, x2=x2@entry=0x7fd8f4, y2=y2@entry=0x7fd8f0) at vikviewport.c:1300 2 0x0457b9d in vik_viewport_draw_line (vvp=<optimized out="">, gc=0xd1c6d0, x1=-159548, y1=19372, x2=-159549, y2=19373) at vikviewport.c:1314 3 0x043644c in trw_layer_draw_track...

gdb shows that it gets stuck in a loop in vikviewport.c at line 1264 (called fom line 1314, 1297) It appears there's quite some documentation on the view port clipping and the comments starting at line 1277 (of vikviewport.c)

Attached test1.vik - I can zoom to 2 pixelfact then it locks goign straight from opening it. (The track lines don't always disappear prior to locj up.) Will set up to compile it local...