[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

19991206: garp widget errors

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 19991206: garp widget errors
  • Date: Mon, 06 Dec 1999 13:03:46 -0700
David,

It could be that your CDE or Motif libraries have been
upgraded or changes, or something is different in the scaling or
offset computation which the X server is using to place the widgets.
Is this something that has changes recently- or always has been off?

If Garp core dumps when trying to read a model data set, you should use
gdinfo to list out the contents of the file. Typically, if something
used to work, and now isn't, then an unidentified grid has come
in and Garp may barf when trying to make a menu item for it.

Things to check include, a grid that gdinfo shows the vertical coordinate 
being blank or a grid with no parameter name. If we know what model
and level or parameter is offensive, we can update the $GEMTBL/grid
tables in your distribution if they are not in sync with those
in the current revision.

Steve Chiswell
Unidata User SUpport




>From: David Fitzgerald <address@hidden>
>Organization: .
>Keywords: 199912061948.MAA12416

>Hi guys, 
>
>We are seeing some widget errors in three of the data panels in Garp.  When th
> e 
>Model Cross-section, Model Time Height or the Model Vertical Profile button is
>  
>chosen, on the resulting panel, the "Level 1" field is not aligned with its 
>corresponding input box.   "Level 1" is skewed downward from where it should b
> e 
>and covers the text below it.  What would cause this to happen and how do I fi
> x 
>it?
>
>In a probably (?) unrelated matter, Garp is core dumping when we try to run 
>Model Time Height  on one particular data set.  The strange thing is that we 
>sucessfully ran the Model Time Height program on this same data set this 
>morning.  What do you need to help me track down this problem?
>
>Dave
>
>++++++++++++++++++++++++++
>David Fitzgerald   
>System Administrator            Phone: (717) 871-2394  
>Millersville University        Fax: (717) 871-4725 
>Millersville, PA 17551                 E-mail: address@hidden
>