Opened 10 years ago

Closed 9 years ago

#305 closed enhancement (fixed)

select point show info

Reported by: chrfi Owned by: harg
Priority: alpha 4 medium Milestone:
Component: LAG Keywords:
Cc: Other processors:

Description

this is a request for the ability to click on a point in the main window or in the profile window and a pop up box to appear listing all the recorded data. this will allow the user to see the exact values rather than the slightly fuzzier graphically interpretations of these values.

the feature will display the closet point when several fall in the same location (so from the top down view this is the highest point)

Change History (6)

comment:1 Changed 10 years ago by harg

Chris, what I need you to do is provide me with a method that will return a string containing the filename of a flightline if I pass it the number assigned to that flightline by the quadtree. You could possibly do it using a vector whose elements are numbered in a way that corresponds with the flightline numbers.

comment:2 Changed 10 years ago by chrfi

I've added a method called getfilename to quadtree which takes a uint8_t which is the flight line number and returns a string which is the full path of the file. (needed to add a tiny get method to the loader classes as well to get the filename)

comment:3 Changed 10 years ago by harg

  • Owner changed from emca to harg
  • Priority changed from alpha 5 to alpha 4 medium
  • Status changed from new to accepted

Thanks Chris. The feature now works, after a fashion. It fulfils its main purpose of identifying flightlines reasonably well as long as the lines do not completely overlap (i.e. as long as there is and area where a flightline is not overlapping with another).

comment:4 Changed 10 years ago by harg

Now works when dragging as well.

comment:5 Changed 9 years ago by harg

Have changed the feature (or, more accurately, fixed it slightly) by stopping it from falling back on point "0" of the bucket when it cannot select anything else. It will now correctly result in "0 0 0". This means it now behaves a lot better in overlap areas. There still appear to be problems getting it to select the correct point, however.

comment:6 Changed 9 years ago by harg

  • Resolution set to fixed
  • Status changed from accepted to closed

DONE! Finally. It now seems to work flawlessly, and does not cause crashes through race conditions any more.

Note: See TracTickets for help on using tickets.