Ed Leafe wrote: > On Nov 23, 2008, at 9:59 AM, Paul McNett wrote: > >> But why is this not an issue in AppWizard-generated apps? > > > Because the data field is not the initially focused control. In > Roger's app, the form opens with the control in question having focus. > If I tab away from that field and then return, the validation fires > correctly, since the underlying _value/_oldval atts hold the actual > data in the field. When the control is the very first control to > receive focus, it's _oldval should be None, but text controls work > differently. > > If I remove line 24 from dDataControlMixinBase.py, the problem goes > away. This is because for text controls, self.Value and self._value > can be different types. Tracing through the code, they are, up until > that point: self._value is None, while self.Value = u''. > > Since this is at the dabo.ui level, and the text control stuff is at > dabo.ui.uiwx, I'm trying to figure out a way to handle this correctly.
Sounds like all we need is a self.Value=None *very early* in the instantiation of text controls (before processing that initial setProperties(), to avoid overriding any settings by the appdev)? Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
