This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Gary, This is Jeff. > > > We held a meeting on the AG today with Jeff re extending ProbeControl to > allow flythrough behavior. Jeff mentioned that we should work on the > latest IDV, 2.2 beta. Could you send the link for the download? I > believe you had some documentation on the new plug-in architecture as > well. > Here are links to the latest stable and the nightly build: http://www.unidata.ucar.edu/software/idv/release/ For the plugin just jar up your .class files. You will also need to include a controls.xml file that tells the idv about your display control. See an example attached. You can load the plugin at runtime with idv -plug <the jar file> - this loads it just the one time idv -installplugin <the jar file> This installs it for later use Or through the Tools->Plugin Manager menu you can load.remove plugins, etc. Also, you can just copy the jar file to your plugins directory: ~/.metapps/DefaultIdv/plugins FYI - the ProbeControl probe point is indeed in X/Y/Z space, not latlon. > > > Thanks for your time and help. > > No problem > > P.S.: Emacs and vi, that's impressive. I'll have to tell my students; > they can't function without intellisense etc. :-) > You can take the text editor out of the developer but you can't take the developer out of the text editor (or something like that). -Jeff Ticket Details =================== Ticket ID: LHT-228930 Department: Support IDV Priority: Normal Status: Closed