Changeset 5374 for trunk


Ignore:
Timestamp:
Apr 30, 2015, 8:58:04 AM (9 years ago)
Author:
ldelgass
Message:

whitespace/comment fixes

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/gui/scripts/flowvisviewer.tcl

    r5368 r5374  
    33#  COMPONENT: flowvisviewer - 3D flow rendering
    44#
    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.
     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.
    88# ======================================================================
    99#  AUTHOR:  Michael McLennan, Purdue University
    1010#  Copyright (c) 2004-2012  HUBzero Foundation, LLC
    1111#
    12 # See the file "license.terms" for information on usage and redistribution of
    13 # 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.
    1414# ======================================================================
    1515package require Itk
     
    134134    private variable _dataset2flow     ;# Maps dataobj-component to a flow.
    135135
    136     private variable _reset 1          ;# Connection to server has been reset
    137     private variable _click            ;# info used for rotate operations
     136    private variable _reset 1          ;# Connection to server has been reset.
     137    private variable _click            ;# Info used for rotate operations.
    138138    private variable _limits           ;# Autoscale min/max for all axes
    139139    private variable _view             ;# View params for 3D view
     
    283283    }
    284284    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"
    286287
    287288    itk_component add zoomin {
     
    960961    }
    961962
    962     # Ensure that the global thickness setting (in the slider settings widget)
    963     # is used for the active transfer-function. Update the values in the
    964     # _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.
    965966
    966967    set value $_settings(-thickness)
     
    10781079#       the slave interpreter.  The purpose is to collect the min/max of the
    10791080#       volume sent to the render server.  Since the client (flowvisviewer)
    1080 #       doesn't parse 3D data formats, we rely on the server (flowvis) to
     1081#       doesn't parse 3D data formats, we rely on the server (nanovis) to
    10811082#       tell us what the limits are.  Once we've received the limits to all
    10821083#       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#
    10841086#
    10851087#       Note: There is a considerable tradeoff in having the server report
     
    16401642#       server parses the 3D data and sends back the limits via ReceiveData.]
    16411643#
    1642 #       FIXME: The current way we generate transfer-function names completely
    1643 #              ignores the -markers option.  The problem is that we are forced
    1644 #              to compute the name from an increasing complex set of values:
    1645 #              color, levels, marker, opacity.  I think we're stuck doing it
    1646 #              now.
    1647 #
    16481644itcl::body Rappture::FlowvisViewer::NameTransferFunction { dataobj cname } {
    16491645    array set style {
     
    16871683    # of the volumes (the first in the list) using the transfer-function as a
    16881684    # reference.
    1689     #
    1690     # FIXME: The current way we generate transfer-function names completely
    1691     #        ignores the -markers option.  The problem is that we are forced
    1692     #        to compute the name from an increasing complex set of values:
    1693     #        color, levels, marker, opacity.  I think the cow's out of the
    1694     #        barn on this one.
    16951685
    16961686    if { ![info exists _isomarkers($tf)] } {
     
    18821872}
    18831873
    1884 # ----------------------------------------------------------------------
    1885 # USAGE: UpdateTransferFunctions
    1886 # ----------------------------------------------------------------------
    18871874itcl::body Rappture::FlowvisViewer::updateTransferFunctions {} {
    18881875    $_dispatcher event -after 100 !send_transfunc
Note: See TracChangeset for help on using the changeset viewer.