It is worth pointing out that an mxODBC-like solution is only required if your
application needs to talk DIRECTLY to an ODBC driver. Stock Python can
communicate with ODBC data sources on Windows through either DAO or ADODB
without any additional software.
···
On Sat, 13 Jul 2002 12:00:49 +0100, Patrick Kimber <patrick.kimber@btinternet.com> wrote:
I understood that the only supported ODBC library for programming in Python
is mxODBC which is expensive for commercial use.
Is this correct?
--
- Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.
So far all the solutions are windows specific. I think there would be some
value in a solution that runs on both linux and windows. mxODBC provides
both but at a price. If the wxWindows ODBC classes work on both windows and
linux that it seems like that would be a good starting point.
···
-----Original Message-----
From: wxpython-users-admin@lists.wxwindows.org
[mailto:wxpython-users-admin@lists.wxwindows.org]On Behalf Of Tim
Roberts
Sent: Monday, July 15, 2002 11:18 AM
To: wxpython-users@lists.wxwindows.org
Subject: Re: [wxPython] ODBC Clases
On Sat, 13 Jul 2002 12:00:49 +0100, Patrick Kimber <patrick.kimber@btinternet.com> wrote:
I understood that the only supported ODBC library for programming in Python
is mxODBC which is expensive for commercial use.
Is this correct?
It is worth pointing out that an mxODBC-like solution is only required if
your
application needs to talk DIRECTLY to an ODBC driver. Stock Python can
communicate with ODBC data sources on Windows through either DAO or ADODB
without any additional software.
--
- Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.
Hy, Is it possible to get rid of the default Button behaviour under Windows,
My current approach is to catch wxEVT_CHILD_FOCUS and reset my desired
default button with wxButton.SetDefault() or wxPanel.SetDefaultItem(None)
if no defaultbutton is desired.
class panel(wxPanel):
....
def __init(self,....):
self.b1=Button(self,-1,"b1",...)
self.b2=Button(self,-1,"b2",...)
self.b1.SetDefault()
if wxPlatform=="__WXMSW__":
self.Connect(-1,-1,wxEVT_CHILD_FOCUS,self._onChildFocus)
def _onChildFocus(self,event):
if self.GetDefaultItem()!=self.b1:
self.b1.SetDefault()
...
How is the current MS-Windows behaviour implemented, is there a better way to
get rid of it?
Greetings, and thank you very much for your answer, Andre'
Are there any differences to know about when putting components on a wxDialog using sizers? I've got code that works great with a wxFrame, but for some reason, I just get a blank window when it's a wxDialog.
Are there any differences to know about when putting components on a
wxDialog using sizers? I've got code that works great with a wxFrame,
but for some reason, I just get a blank window when it's a wxDialog.
In some situations you need to force the layout to happen on a wxDialog.
This is because the wxDialog doesn't get an initial size event when shown,
so the default size handler isn't called (which is where Layout is called.)
Try calling Layout() after you've put all the controls and the sizer on the
dialog.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!