| Quote (dumketu @ Jan. 30 2007,7:17) |
- I have noticed that when you manually edit a waypoint's coordinates, you have to close the properties box and re-open it before the coordinates show the update. It might be helpful if the coordinates changed as soon as the edit box is closed. (I wasted some time initially thinking the program was not taking my changes since I did not see the update immediately).
- When loading a new user map, the program does not automatically default to the map you are trying to load. It takes the first map in the list if the dialog was just opened or the last one you were working on if the dialog had not been cloed. This is workable, but I have probably had to fix the first map a dozen times as I was rushing through installing a bunch of maps.
- Lastly, a fourth calibration point would be helpful in some instances. I have been using images of 1:250,000 maps downloaded from the University of Texas Library for parts of India, and I realized that the maps are not quite square. (at first I thought this was just due to the curvature of the earth and the fact that the longitude lines converge at the pole, but this seems to be exagerated by the way the maps were scanned). This problem also occurs when I try to photograph a map and don't quite get it centered. A fourth point would enable the map to be skewed to correct for this. |
Hi Brian.
Thanks much for the suggestions.
1 - (waypoint updating). Yep, we need to get it synching. Unfortunately it's not as easy as it would seem. One thing is you can hit the 'refesh' button on the dialog to get the current changes. You don't have to open/reopen.
2 - Very good point. This is very annoying and the same thing was happening to me. I fixed it so that the bottom frame on the dialog is automatically selected on the user map just added. Much better now.
I just put up a new v3.0 with this fix and a few other improvements in the user map area. I was able to speed display up quite a bit when you have many maps opened. As long as all your maps aren't on the screen at once, it should be much faster (with a subset of maps on the screen). Also, in a future version I should be able to
halve the loading time for jpegs. It now goes to a hourglass while loading, at least!
Finally, I'm curious about the crash(es) you got while loading maps and trying to do something else. TF shouldn't respond at all while loading a user map -- it takes the focus away from the program. Other programs should be fine. I've tried but can't seem to reproduce this crash.
3 - 4th calibration point. Yep, it would help. Requires a different algorithm to solve the fit equations, but it shouldn't be too hard to add. It would then work for 4+ points. As many as you want... though it becomes more sensitive to errors (it's a least squares, overconstrained problem).
Thanks again for the feedback.
