I was specifically thinking of the components that only used a subset of the Alignment enum values, and was thinking of what happens when we want to create some kind of GUI builder, which is going to need to know these kinds of restrictions.
But I suppose that can easily enough be fixed by building a small amount of custom knowledge into a GUI Builder. Reminder to self - when exposing design-time meta-data, don't try to solve every last piece of the puzzle - the last 1% can be a real sink-hole. On Thu, Apr 9, 2009 at 17:55, Greg Brown <[email protected]> wrote: > >>(*) Component#StyleDictionary should expose methods for getting the >>valid values of an enum property, >>since some methods will take an enum, but will only be valid for some >>subset of the values on that enum (e.g. usage of VerticalAlignment) > > Possibly, though this may be better served via documentation. A skin wouldn't > be expected to programmatically provide info on the range of valid float > values for a style property, for example. >
