From: Norman V. <nh...@ca...> - 2001-10-02 22:29:34
|
Jim Wilson writes: >Norman Vine <nh...@ca...> said: > >> I really have to figure out what is causing the cursor to >lose focus :-( >> > >Do you mean in the input widget? Probably all it needs is an explicit >activate since I'm just reusing the same object. This maybe only a WIn32 phenomena Where the cursor sometimes disappears and you have to something like double right click to get it back. >Actually what I was thinking was maybe an expansion of the property browser to >use XML definitions of data attributes (valid values or rangers) and then a >gui attribute per property that could one of a predefined set of classes. >Right now the only one is the propEdit widget, but we could have >propDropDownSelect, propRadioButtons, propLargeInputs, etc. Validation could >also be included. These attributes would need to be added to the property.xml > definition since they could vary by property. This is a good idea. My guess is that this wants to be in the actual C Code instead of the XML script We could probably do this by having new classes that contain the actual value and its acceptable range and then the XML script would point to the appropriate C variable. ie any variable that was settable from a ui of any form would be derived from one of these 'super types'. It could be that a puValue object is a good base class ? This is close to what I was alluding to when I suggested an XML inteface to PUI. >As far as call backs, all we'd need is the one thats there for updating >the properties (now in the propEdit class). The fgTie could handle any >special processing. For example, we could have a property for Starting >Airport and then the fgTie callback could call the teleport routine. BTW have you noticed the similarity between the getters and setters in PUI and in the Properties module. It almost seems as if all we need is a fgTie( puValue, fgProperty) or maybe even a fgTie( puObject, fgProperty); but I am not a properties expert by any means. Cheers Norman |