search

Letractively / choosel

Automatically exported from code.google.com/p/choosel
0 stars 0 forks source link

Switching between calculation resolvers does not keep currently selected property (if possible) #173

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a visualization that contains a number mapping
2. Set it to Maximum
3. Set the resolver to a non-default property
4. Switch the resolver to Minimum

What is the expected output? What do you see instead?
The previously selected property should also be used for the newly selected 
resolver, if this is possible. However, it is switched back to the default 
(first) applicable property.

Original issue reported on code.google.com by Lars.Grammel on 17 Jul 2011 at 11:01