NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
> > That said - the problem is in the displays in your bundle. When you first > load up the original bundle the data source is in error and the displays > won't be created. You can go and change the data source to point to something > that works but the displays aren't there. We'll have to figure something out > to deal with this scenario. > Hi Bill, Well I did figure something out. It will be in tonight's (Tuesday's) build. When you load in the bundle that's bad you should run the idv with the command line argument: idv -Dcontrol.ignoreerrors=true This causes the display controls to still kept around when they encounter an error but you just won't see them. Then, you will get your data error. Afterwards change the data source (right clicking on it and select "Change Data"). Then save the state off in a bundle. This should include the display controls that had encountered the original error. Then reload the bundle and you should be seeing the new data with the original displays. I know its a little tricky but, well, it is a little tricky :-) -Jeff Ticket Details =================== Ticket ID: CVW-281659 Department: Support IDV Priority: Normal Status: Closed