Ignore:
Timestamp:
Apr 4, 2012 2:15:10 PM (12 years ago)
Author:
ldelgass
Message:

Fix for sequence result - nanovis can only handle "points-on-mesh" type if
it is a uniform mesh, otherwise send to vtk. Also, it type is empty, set it
to auto (which will choose nanovis currently). This fixes a problem with tools
like omen nanowire. That tool specifies a sequence element with 2 components:
the first is dx data, the second only has a style. This is really a bug in the
tool: the style should be inside the first component. However, the last
component seems to determine the type of the field as a whole, so it gets set
to nothing since there is no data in the second component.

File:
1 edited

Legend:

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

    r2889 r2939  
    493493                        set fmt [$dataobj type]
    494494                        switch -- $fmt {
    495                             "opendx" - "dx" - "points-on-mesh" {
     495                            "points-on-mesh" {
     496                                set mesh [$dataobj mesh]
     497                                set fmt [expr {("" != $mesh) ? "vtk" : "nanovis"}]
     498                                set extents [$dataobj extents]
     499                                if { $extents > 1 } {
     500                                    set fmt "flowvis"
     501                                }
     502                            }
     503                            "opendx" - "dx" {
    496504                                set fmt "nanovis"
    497505                                set extents [$dataobj extents]
     
    499507                                    set fmt "flowvis"
    500508                                }
     509                            }
     510                            "" {
     511                                set fmt "auto"
    501512                            }
    502513                        }
Note: See TracChangeset for help on using the changeset viewer.