TUPLOT External: Difference between revisions

Browse history interactively

← Older edit

Content deleted Content added

VisualWikitext

Revision as of 10:52, 2 March 2018 view source Ellis Symons (talk \| contribs) Bureaucrats, Administrators 3,095 edits →Planned Future Enhancements ← Older edit		Latest revision as of 00:46, 30 November 2023 view source ElizaCollison (talk \| contribs) Bureaucrats, Administrators 3,894 edits No edit summary
(One intermediate revision by the same user not shown)
Line 16: <br> [[File: TuPLOT_viewer.PNG]] ~~=Planned Future Enhancements=~~ ~~Planned future enhancements include:~~ Full functionality from the TUFLOW QGIS plugin Secondary axis ARR2016 functionality (pulling statistics from results) Opening multiple .tpc files at once Exporting data from display Enhance viewer association with ArcGIS Exit with ArcGIS Minimise with ArcGIS Window always in front of ArcGIS but not always topmost ~~<b>If you have any suggestions on additional functionality or improvement, or find a bug, please email a description to support@tuflow.com</b><br>~~ =How it works= Line 34 ⟶ 21: The stand alone TuPLOT viewer uses Python (the package installed with ArcGIS) as a base for the viewer. ArcGIS and the TuPLOT viewer communicate using an interface file (.int) that is written by ArcMap and read by TuPLOT. The .int file is written automatically when TuPLOT is initiated and deleted when TuPLOT is closed. If TuPLOT crashes, the .int file may not be deleted. If this occurs many times, a build up of .int files may occur in the same folder as the .tpc. The user should feel free to delete these manually if this occurs without fear of interfering the the TuPLOT viewer. The user may also manually select a desired *.int file using the <b>Set Interface File</b> button in the TuPLOT window, though generally this should not be required. ~~The stand alone TuPLOT viewer is also planned to be made available in both QGIS and Mapinfo.~~