…nto uvcdat-master

…had before.

I have no clue about why, but if you let it try, it will crash.
These changes make sure that animations don't happen.

…ead. This should make it clear

 that that class is part of a workaround to a GUI bug (if you clear a cell, the contents don't
 change visibly, although they do get cleared internally) and no more.  Also, the other changes
 check for None.
2. When the spreadsheet cell (graphics pane) should be blank, we now:
  (1) call clear_cell on it
  (2) make a uvc_zero_plotspec (a pseudo-blank plot) and plot it
  (3) call clear_cell on it again
This change seems to reduce but not eliminate the possibility that you'll get a segfault
upon clicking on a blank pane (the click should just select it for use in the menu on top,
and draw a blue highlight to confirm your selection).

I've run out of workarounds.  To do any better, we'll have to fix the Vistrails GUI which
all this is built on top of.

…me how.

…ching a bogus file)

…-master

…at-master

Conflicts:
	vistrails/gui/uvcdat/diagnosticsDockWidget.py

…grid' into uvcdat-master

…to uvcdat-master

Disallow vtkWebApplication as a module and catch NotImplementedErrors
for abstract class.  Also update vtk_parser.py to include Prabhu's
updates for VTK6.

…nd do so).

Also, some useless debugging output is deleted.

…strails into uvcdat-dv3d-add_dv3d_vcs_templates

…nto uvcdat-master

…ls into uvcdat-dv3d-vcs-integrate_usg

Issues 524 and 526.

…-integrate_usg

…ls into uvcdat-dv3d-vcs-integrate_usg

…ls into uvcdat-dv3d-vcs-integrate_usg

The issue is that the caught exception didn't quit UV-CDAT so the
other events attempted to start, causing things to hang.

Default noDebugPopups to True and get rid of console logger. ** Note:
you will either have to set noDebugPopups to True in
~/.uvcdat/startup.xml or delete your ~/.uvcdat directory to see the
effects. **

Since sys.stderr is usually written to a file, we need to make sure
the error is written to the real stderr.

If we have sys.stderr redirected, write the message to the redirected
stream, too.

…o uvcdat-master

This particular type of error might be expected if you are loading
packages non-interactively. They are not application-level errors, they
just indicate that the package cannot be used.

This makes VistrailsStartup ask the PackageManager not to report missing
dependencies if we are running for the first time (i.e. it just
installed the default startup.xml file).

Conflicts:
	vistrails/core/modules/package.py

Reverts b789680, 3a96b07, c354158.

…er' into uvcdat-master

…ages_master' into uvcdat-master

…aster' into uvcdat-master

Fixes 447841f, MissingRequirement should disable the package just like
InitializationFailed does.

Note that this branch includes the uvcdat_cdattoolbar branch.

*** This branch should be updated in unison with the corresponding
uvcdat-490-animation-updates in the uvcdat-devel repo. ***