I have an application that is required to:
A) run on windows NT and UNIX
B) access an activeX control when running on NT
I'm running into problems with the GUI interface. If I use Tkinter, I
can
write my GUI for both NT and UNIX no problem, but I need pythonwin to
use
the activeX control and Tkinter and pythonwin don't like each other.
So, one possiblility is to use a different tool for writing the GUI.
Does wxWindows get along with pythonwin? Any other suggestions?
BTW, The activeX control doesn't provide any user interface elements.
Rather, it provides access to a proprietary data file format used by a
mass spectrometer we have. Access to the data files is implemented in
shared libraries on the UNIX platform, so I don't have any problems
there.
I also tried moving the access to the activeX control into a C++
extension for python. The idea was to use MFC to create the extension,
and during the initalization of the module, an invisible, modeless
dialog would be created that contained the ActiveX control.
Unfortunately, the call to CDialog::Create always fails. I'd guess this
has something to do with missing message queues, since there's no MFC
main window providing the message queue, but I don't for sure, and even
if I am right, I don't know how to fix it. Anyone have any ideas on
what might be causing this problem and how to fix it? Getting this
working would probably be the easiest approach for me, because then I
wouldn't have to learn a new GUI toolkit.
Tom Fenn
A) run on windows NT and UNIX
B) access an activeX control when running on NT
I'm running into problems with the GUI interface. If I use Tkinter, I
can
write my GUI for both NT and UNIX no problem, but I need pythonwin to
use
the activeX control and Tkinter and pythonwin don't like each other.
So, one possiblility is to use a different tool for writing the GUI.
Does wxWindows get along with pythonwin? Any other suggestions?
BTW, The activeX control doesn't provide any user interface elements.
Rather, it provides access to a proprietary data file format used by a
mass spectrometer we have. Access to the data files is implemented in
shared libraries on the UNIX platform, so I don't have any problems
there.
I also tried moving the access to the activeX control into a C++
extension for python. The idea was to use MFC to create the extension,
and during the initalization of the module, an invisible, modeless
dialog would be created that contained the ActiveX control.
Unfortunately, the call to CDialog::Create always fails. I'd guess this
has something to do with missing message queues, since there's no MFC
main window providing the message queue, but I don't for sure, and even
if I am right, I don't know how to fix it. Anyone have any ideas on
what might be causing this problem and how to fix it? Getting this
working would probably be the easiest approach for me, because then I
wouldn't have to learn a new GUI toolkit.
Tom Fenn