Goo idea, but then you need put the keys in their own dict inside of
the userInfo, like "EntityModeler" = {isIndexed=true;} as for
example, we have keys like isLocalized or isIndexed, too.
Cheers, Anjo
Am 19.07.2006 um 15:47 schrieb Mike Schrag:
> After thinking about this one and Garry's index suggestion, I'm
> thinking I should write things like this into userInfo, but not
> make it visible to the users of the modeler. So when it loads in,
> we would read these things out of userInfo and write them back out
> in userInfo, but remove them from userInfo while you're using
> modeler (basically just using userInfo for persistence). That way
> you can get to these things, but it won't pollute the UI.
This archive was generated by hypermail 2.0.0 : Wed Jul 19 2006 - 10:00:51 EDT