When Visualizations are created, two of the things that are defined are the
initial default slot mappings (SlotMappingInitializer), and the
VisualMappingsControls, which control what options there are for the user to
change those mappings (ie the mappings panel on the side of each view).
The problem is that, despite the SlotMappingInitializer being extended and
customized for each of the Choosel Applications, the Visual Mapping Controls
are always set to the same 5 resolvers.
This causes several problems:
1. Sum is displayed as the default value for Label Size, but in actuality, the
resolution of that slot may happen in any number of ways.
2. Custom slot resolvers are not appearing among the Mappings options, and so
initial default mappings are being lost as soon as you change how a slot is
resolved.
We should find a way to introduce some sort of dependancy on the initial
default slot resolvers, and the Visual Mappings Controls available to the user.
Original issue reported on code.google.com by patrickc...@gmail.com on 18 May 2011 at 5:08
Original issue reported on code.google.com by
patrickc...@gmail.com
on 18 May 2011 at 5:08