I'm running on NT4, and have run into the previously reported bug where
opening a wxFileDialog disables the cursor keys in a styled text control.
The app I am working on uses PyCrust to provide an environment for
manipulating data files via Python, and a file dialog is used to select the
data file to manipulate. With this bug, as soon as a data file is open,
the interactive manipulation part becomes annoyingly difficult.
Is there a fix for this bug or a workaround? I can't change to a non WinNT
platform. Does this bug occur with custom dialogs derived from wxDialog?
If not, has someone written a dialog for opening and saving files that I
could use? Or, is there a nice wxPython GUI interface to the python
interpreter that does not rely on the styled text control?
I've put a lot of work into developing various views of the data files
based on wxPython, but this problem seems to be a show stopper.
I don't have a solution to your problem, but I can offer one possible
alternative. As much as I could, I have kept PyCrust's dependency on wxSTC
to a minimum, and have tried to isolate the parts that use wxSTC. So it
wouldn't take too much effort (I think) to create a PyCrust version that
used a regular text control. Of course, you then give up all the wonderful
features of the wxSTC, like colorized code, call tips, autocompletion popup
lists, etc. But there might be ways to even duplicate that functionality, if
you were determined. The data is still fed to those features by PyCrust, and
gathering that data is a completely independent function (see the
interpreter.py and introspect.py modules). Let me know if this is something
you end up considering and I could give you some pointers, or possibly
create a variation that does this.
P.S. I'm curious to learn more about your application? Is it available
anywhere?
I'm running on NT4, and have run into the previously reported bug where
opening a wxFileDialog disables the cursor keys in a styled text control.
The app I am working on uses PyCrust to provide an environment for
manipulating data files via Python, and a file dialog is used to select the
data file to manipulate. With this bug, as soon as a data file is open,
the interactive manipulation part becomes annoyingly difficult.
Is there a fix for this bug or a workaround? I can't change to a non WinNT
platform. Does this bug occur with custom dialogs derived from wxDialog?
If not, has someone written a dialog for opening and saving files that I
could use? Or, is there a nice wxPython GUI interface to the python
interpreter that does not rely on the styled text control?
I've put a lot of work into developing various views of the data files
based on wxPython, but this problem seems to be a show stopper.
Not yet. I don't have an NT4 box anymore so without being able to duplicate
it I am unable to fix it.
I can't change to a non WinNT
platform. Does this bug occur with custom dialogs derived from wxDialog?
Don't know, try it and see. My guess is that it doesn't.
If not, has someone written a dialog for opening and saving files that I
could use?
The wxFileDialog used for wxGTK and other platforms is completely wx (has no
native code) so you could probably port it to wxPython pretty easily. Look
in the wxWindows source tree are include/wx/generic/filedlgg.h and
src/generic/filedlgg.cpp.
I've put a lot of work into developing various views of the data files
based on wxPython, but this problem seems to be a show stopper.
Frustratedly,
If you are able, channeling some of your frustrations into firing up the
debugger and tracing through the code would be real helpful.
···
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters? http://wxPython.org Relax with wxPython!
It seems to be fixed in 2.3.2b5 - can reproduce it (both in my app and in
the demo) in 2.3.1 but not in 2.3.2b5.
···
--
Richie Hindle, rjh@cyberscience.com
All opinions are mine and not necessarily those of my employer.
Why did the Zen Buddhist refuse anaesthetic at the dentist?
Because he wanted to transcend dental medication.
It seems to be fixed in 2.3.2b5 - can reproduce it (both in my app and in
the demo) in 2.3.1 but not in 2.3.2b5.
Cool! I love it when bugs fix themselves. (Actually, I've upgraded the
version of Scintilla that I'm using so there must be some change there that
affected it.)
Now if we could get the ActiveX on Win9x bug to fix itself we'll be all set,
<wink>
···
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters? http://wxPython.org Relax with wxPython!
Cool! I love it when bugs fix themselves. (Actually, I've upgraded the
version of Scintilla that I'm using so there must be some change there
that
affected it.)
Aargh! I much prefer to understand why bugs happen as it means less
chance of the code regressing back to the bug There is also a lot of
satisfaction in beating a bug into submission.
I just like it when either of you fix a bug. I don't really care how you do
it. <wink>
···
---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."
-----Original Message-----
From: wxpython-users-admin@lists.wxwindows.org
[mailto:wxpython-users-admin@lists.wxwindows.org]On Behalf Of Neil
Hodgson
Sent: Friday, October 12, 2001 4:14 PM
To: wxpython-users@lists.wxwindows.org
Subject: Re: [wxPython] bitten by the wxFileDialog wxSTC bug
Robin Dunn:
> Cool! I love it when bugs fix themselves. (Actually, I've upgraded the
> version of Scintilla that I'm using so there must be some change there
that
> affected it.)
Aargh! I much prefer to understand why bugs happen as it means less
chance of the code regressing back to the bug There is also a lot of
satisfaction in beating a bug into submission.
There is also a lot of