I've been meaning to do this for some time - here's a PickList module that enables you to manage Pick interactions. It takes three parameters: the output of Pick, a radius, and a reset. I've included a makefile that creates a dxexec including the new module (cygwin; modify it for other platforms or run-time loading), a .mdf file, and an example net. To run it, build dxexec, then
dx -edit picklist -exec ./dxexec -mdf picklist.mdf and put in it exec on change. Up comes an image of a quad. Enter Pick mode (control-I in the Image window) and pick. Up comes a glyph at the pick point. Pick again, and the new point is added. Pick very near a previous pick and the picked pick disappears. And so on. The radius parameter determines the max distance between a new pick and an old pick that will cause the old pick to be removed, rather than adding a new point. The reset resets the list to empty. (I'm attaching a tar gz - I have a feeling that attachments don't work in the mailing list. If I see my note on the mailing list w/out the attachment, I'll send it out some other way) Greg (See attached file: picklist.tar.gz) Chris Pelkie <[EMAIL PROTECTED]>@opendx.watson.ibm.com on 07/09/2001 07:47:11 AM Please respond to [email protected] Sent by: [EMAIL PROTECTED] To: [email protected] cc: Subject: Re: [opendx-users] Creating picks >I want to draw line on some data map and I use picks to do it. > >To draw line properly I want to zoom in and I can see only part of my >map. >When I create some picks and try to navigate (or zoom out) picks created >before >becomes NOT picks (bacause execution completes) . > >How can I join two portions of picks? Should I use something lile >SetLocal or SetGlobal? > >Thanks. > I've done something similar (many times), but using ProbeList. Pick returns data value(s) and location, Probe and ProbeList only locations (and not based on a ray intersection, so you have to rotate the view to set the proper depth for each Probe point). Also there's no insert/delete from the middle of a ProbeList, so practice, then do it right the first time. There is no PickList module. For no good reason, in the Image controls, Probe is called Cursor. Helps to Glyph the ProbeList so you see visible items to manipulate as you tweak. You can send the ProbeList as the first input to Construct, then ShowConnections, to see the connected line. If you also Glyph the positions and Collect with ShowConnections output, you'll see a string of "pearls". In Execute on Change mode, you can manipulate one pearl at a time to change the shape more or less interactively. When you get far enough along in opendx understanding, you can generate a rough ProbeList by looking straight down on the map and clicking the path out, then Map your 'map' data onto the probe connected path to auto-generate the appropriate heights. Now you have the land-crawler path. Add an offset with Compute if you want to 'fly over' the terrain in terrain-following mode (like a cruise missile). Or just add a fixed offset to get a fixed altitude flight above the terrain. Chris Pelkie Vice President/Scientific Visualization Producer Conceptual Reality Presentations, Inc. 30 West Meadow Drive Ithaca, NY 14850 [EMAIL PROTECTED]
picklist.tar.gz
Description: Binary data
