Page 1 of 1
[FIXED] BUG Point Picking Display Box Values
Posted: Fri Feb 28, 2014 7:54 am
by MJS
The Point Picking tool display box in Version: 2.5.3 [Windows 64 bits] should show # "point number"(x,y,z) values but instead displays the # "point number"("point number",x,y). The point number is displayed instead of the x value and x value instead of the y value and y instead of the z value.
Re: BUG Point Picking Display Box Values
Posted: Fri Feb 28, 2014 8:05 am
by daniel
I can't reproduce the bug... Here is what I get:
- cc_point_list_picking_2.5.3.jpg (32.93 KiB) Viewed 5280 times
Can you post a snapshot?
Re: BUG Point Picking Display Box Values
Posted: Fri Feb 28, 2014 8:09 am
by daniel
My bad, you were referring to the simple point picking tool which spawns "2D labels"... I acknowledge the bug ;)
- cc_point_label_picking_2.5.3.jpg (11.79 KiB) Viewed 5280 times
Re: BUG Point Picking Display Box Values
Posted: Fri Feb 28, 2014 8:48 am
by MJS
Should have added a snapshot to make it clearer!
Re: BUG Point Picking Display Box Values
Posted: Sun Mar 09, 2014 11:33 pm
by stevewillis
This one just got me. It appears to affect both the label and property display of points and vectors picked with the simple point picking tool. I don't presently see a way to get the actual coordinates of my vectors.
Re: BUG Point Picking Display Box Values
Posted: Mon Mar 10, 2014 7:18 am
by daniel
Yes it has already been reported (and fixed in the trunk version).
Have you tried with the "point list picking" tool?
Re: BUG Point Picking Display Box Values
Posted: Mon Mar 10, 2014 8:17 pm
by stevewillis
Yes, the "point list picking" tool works great. I use both tools, and have different use cases for each. In this particular case, I need to display the vectors that the simple "point picking" tool draws between pairs of points, and also need to get the x, y, and z offsets independently for these points. As a workaround, I exported the points in my cloud to an ASCII file, and then just looked up each point in my vectors from that file by point number.
Nothing urgent. I just wanted to "vote" for this bug if it hadn't been addressed, and also call attention to it since it has only appeared in the latest OSX version, to my knowledge. Thanks for an excellent analysis application!