On Tuesday 27 April 2010 10:05:33 am Paul McNett wrote: > On 4/27/10 9:45 AM, Jeff Johnson wrote: > > Guys: I solved the problem of the button not showing up. On Windows it > > shows up behind the label. On Linux it shows up on top of the label. > > I guess it comes down to attitude of the platform developer. Windows wants > to make sure you've read all relevant text before being able (or not being > able) to push the button. And Linux believes people learn how things work > by fiddling with buttons, even if they haven't or can't read accompanying > text. > > :) > > Seriously, there must me a missing sizer.append() call somewhere... > > Paul
LOL :-) I wish it was just "attitude". I found many interesting differences between the two platforms. For some reason Linux will allow mistakes like forgetting a sizer.append() without warning. But you always see the object somewhere on the form. But windows often does not even display the object (may be off the screen) and does not report the error. Windows and dialogs are a real problem too. Windows often hides the dialog behind some other object or form. So it is required that the parent (of the dialog) be set. This is really obvious when using several modal dialogs each on top of the other. On Linux dialogs do a better job of determining the parent for some reason. But I always pass the parent now. dTextBox acts very different on the two platforms. Try using "selectOnEntry = True" and they act very different. I believe there are more but can't recall any others at the moment. Then there is the differences between the two pythons. Windows works well with recursive code while my linux always has trouble. Not sure what that's about. I'll bet there is a difference between the SQLite's too. Johnf _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
