- Timestamp:
- Apr 30, 2015, 8:58:04 AM (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/gui/scripts/flowvisviewer.tcl
r5368 r5374 3 3 # COMPONENT: flowvisviewer - 3D flow rendering 4 4 # 5 # This widget performs volume and flow rendering on 3D scalar/vector datasets.6 # It connects to the Flowvis server running on a rendering farm, transmits7 # data, and displays the results.5 # This widget performs volume and flow rendering on 3D scalar/vector datasets. 6 # It connects to the Flowvis server running on a rendering farm, transmits 7 # data, and displays the results. 8 8 # ====================================================================== 9 9 # AUTHOR: Michael McLennan, Purdue University 10 10 # Copyright (c) 2004-2012 HUBzero Foundation, LLC 11 11 # 12 # See the file "license.terms" for information on usage and redistribution of13 # this file, and for a DISCLAIMER OF ALL WARRANTIES.12 # See the file "license.terms" for information on usage and redistribution of 13 # this file, and for a DISCLAIMER OF ALL WARRANTIES. 14 14 # ====================================================================== 15 15 package require Itk … … 134 134 private variable _dataset2flow ;# Maps dataobj-component to a flow. 135 135 136 private variable _reset 1 ;# Connection to server has been reset 137 private variable _click ;# info used for rotate operations136 private variable _reset 1 ;# Connection to server has been reset. 137 private variable _click ;# Info used for rotate operations. 138 138 private variable _limits ;# Autoscale min/max for all axes 139 139 private variable _view ;# View params for 3D view … … 283 283 } 284 284 pack $itk_component(reset) -side top -padx 2 -pady 2 285 Rappture::Tooltip::for $itk_component(reset) "Reset the view to the default zoom level" 285 Rappture::Tooltip::for $itk_component(reset) \ 286 "Reset the view to the default zoom level" 286 287 287 288 itk_component add zoomin { … … 960 961 } 961 962 962 # Ensure that the global thickness setting (in the slider settings widget)963 # is used for the active transfer-function. Update the values in the964 # _settings varible.963 # Ensure that the global thickness setting (in the slider 964 # settings widget) is used for the active transfer-function. Update 965 # the values in the _settings varible. 965 966 966 967 set value $_settings(-thickness) … … 1078 1079 # the slave interpreter. The purpose is to collect the min/max of the 1079 1080 # volume sent to the render server. Since the client (flowvisviewer) 1080 # doesn't parse 3D data formats, we rely on the server ( flowvis) to1081 # doesn't parse 3D data formats, we rely on the server (nanovis) to 1081 1082 # tell us what the limits are. Once we've received the limits to all 1082 1083 # the data we've sent (tracked by _recvdDatasets) we can then determine 1083 # what the transfer functions are for these # volumes. 1084 # what the transfer functions are for these volumes. 1085 # 1084 1086 # 1085 1087 # Note: There is a considerable tradeoff in having the server report … … 1640 1642 # server parses the 3D data and sends back the limits via ReceiveData.] 1641 1643 # 1642 # FIXME: The current way we generate transfer-function names completely1643 # ignores the -markers option. The problem is that we are forced1644 # to compute the name from an increasing complex set of values:1645 # color, levels, marker, opacity. I think we're stuck doing it1646 # now.1647 #1648 1644 itcl::body Rappture::FlowvisViewer::NameTransferFunction { dataobj cname } { 1649 1645 array set style { … … 1687 1683 # of the volumes (the first in the list) using the transfer-function as a 1688 1684 # reference. 1689 #1690 # FIXME: The current way we generate transfer-function names completely1691 # ignores the -markers option. The problem is that we are forced1692 # to compute the name from an increasing complex set of values:1693 # color, levels, marker, opacity. I think the cow's out of the1694 # barn on this one.1695 1685 1696 1686 if { ![info exists _isomarkers($tf)] } { … … 1882 1872 } 1883 1873 1884 # ----------------------------------------------------------------------1885 # USAGE: UpdateTransferFunctions1886 # ----------------------------------------------------------------------1887 1874 itcl::body Rappture::FlowvisViewer::updateTransferFunctions {} { 1888 1875 $_dispatcher event -after 100 !send_transfunc
Note: See TracChangeset
for help on using the changeset viewer.