Skip to content
This repository has been archived by the owner on Aug 29, 2023. It is now read-only.

Open Dataset dialogue keeps values from previous selection #417

Closed
forman opened this issue Sep 25, 2017 · 2 comments
Closed

Open Dataset dialogue keeps values from previous selection #417

forman opened this issue Sep 25, 2017 · 2 comments
Assignees
Milestone

Comments

@forman
Copy link
Member

forman commented Sep 25, 2017

From @gunbra32 on June 22, 2017 8:25

Expected behavior

I would expect the Open Data Set dialogue to be either empty or pre-filled with values corresponding to the actual dataset to be opened.

Actual behavior

When choosing to open a second dataset, the values for variable and time constraint from the previous dataset are showing up in the dialogue box. In the example shown below, the proposed time constraint is Out of range and the variable constraint is from the previously opened aerosol product and not from the FIRE dataset.

snip_20170622102409

Steps to reproduce the problem

  1. Open an arbitrary dataset.
  2. Open a second arbitrary dataset.

Note that I observed this behaviour when step 1 failed dut to the unavailability of esa_cci_odp. I am currently not able to test if it the described behaviour also occurs after an successful opening as the esa_cci_odp is nor working for me at the moment.

Specifications

Windows 10
[email protected]
Provide information such as the version of the project, operating system, or hardware.

Copied from original issue: CCI-Tools/cate-desktop#20

@forman
Copy link
Member Author

forman commented Sep 25, 2017

The idea was to let users open/download data from the same spatial/temporal subset across multiple data sources. I agree, that this approach must be intersected with the actually available spatial/temporal coverage.

What about having named subset configurations that are stored with the app and which you can apply to any data source just by selecting the subset's configuration name? Each subset configuration contains

  • spatial range
  • time range
  • variable(s) names

@forman
Copy link
Member Author

forman commented Sep 25, 2017

From @mzuehlke on August 15, 2017 8:44

Bug filed by @HerzogStephan and @HelenClifton mentioning related problems:

@forman forman added the gui label Sep 25, 2017
@forman forman added this to the 1.0 milestone Sep 25, 2017
@forman forman assigned mzuehlke and unassigned forman Sep 25, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants