Ed Leafe wrote: > On Nov 14, 2007, at 4:52 AM, VGSoftware wrote: >> I added some debugging prints around and this is what i found: >> It seems like as soon as i add a mask all of the dTextBoxes become >> wx.lib.masked.TextCtrl and not plain simple wx.TextCtrls > > I don't understand why this happens, but somewhere the wires are > getting crossed. The problem is not that the subsequent controls are > masked.TextCtrl (checking the type or using isinstance() will show > that), but that the code *thinks* that they are masked, and calls > methods as if they *were* masked controls. Remember, if they truly > were masked controls, they *would* have the _autofit attribute. > > There is a a lot of sleuthing to do here. I may have the time to dig > into this later.
Quick question regarding this (haven't dug into it at all): is there a reason we don't make dTextBox descend from the wx masked textbox regardless of whether the Masked property is set? IOW, why not let all dabo textboxes have masking ability all the time and not just when we remember to set the property in the constructor? >> BTW, you guys know you rock right? Yeah, we know we rock, but we still love to hear it! :) >> Dabo is really turning into a GREAT framework, it still need polish as >> you well know, but it has my full confidence. >> I hope i helped in getting it to be PERFECT, and i also hope i will >> help >> more! > > Welcome aboard, and thanks for the compliments! The more people who > get involved, the better the framework will become. I second that. -- pkm ~ http://paulmcnett.com _______________________________________________ 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/dabo-users/[EMAIL PROTECTED]
