simple question. I have created a chm help file that I want
to start when the >help< button of my menubar is pressed.
(Windows)
How? I have tried spawn.. and execv.. without success.
thanks
marcus
import sys,webbrowser
if sys.platform='win32':
webbrowser.open('help.chm')
else:
webbrowser.open('help.html')
Stani
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
How do I reseove this. While it's unlikly someone will just play all
AI's it is useful for debugging ourposes.
You have to allow program control to return from the event handlers to
the MainLoop in order for screen updates and other things to occur.
Your AI loop probably needs to be unrolled and invoked one step at a
time from a timer or perhaps an EVT_IDLE handler. Each step should do
its thing and then return.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
I am using this from a notebook window so I don't know if that is part
of the issue. It looks very promising at this point.
Thanks
Mike
I maintain an experimental modded version of the BitTorrent reference
client at http://bt.degreez.net . For the past few weeks I've been
chasing a bug that seems to be corrupting data downloaded by the
client. It is very elusive, only striking certain Windows-based
machines (and not me directly, which certainly doesn't help my debugging
efforts), and doesn't seem to be related to the operating system
version (98, XP, etc) or disk format. One user who's been plagued by
the problem recently reported an application error; ' The instruction at
"0x1e041568" referenced memory at "0x05000054". The memory could not be
"read". ' I suspect a problem with certain system DLLs being accessed
via wxWindows.
I would appreciate if:
1. Someone could get me a list of the system DLLs wxWindows accesses in
its performance, so I can gather information about them and try to
correlate them with users with the problem.
2. Someone would go over my source code and make sure I'm not doing
something that's causing the window-building to go awry. The source is
available at
http://home.elp.rr.com/tur/BitTorrent-experimental-S-5.8.5.zip or
http://home.elp.rr.com/tur/BitTorrent-experimental-S-5.8.5.tar.gz and
the only file you'll need to audit is "btdownloadgui.py".
To anyone willing to help me, thanks in advance. :-)
wxWakeUpIdle()
Get a copy of DependencyWalker from http://www.dependencywalker.com/ and
run it on wxc.pyd.
GREAT tip. Thanks!
1e041568 is inside python23.dll, somewhere around the PyArg_* and
PyObject_GC_* handlers. Maybe an argument issue in the Python/C
interface, or a garbage collection problem.
Have you used Dr. Watson to try to get a traceback?
--
- Tim Roberts, ti...@probo.com
Providenza & Boekelheide, Inc.
Like I said, I've never experienced the problem myself; I've only gotten
reports from users. Further, these users almost never get that sort of
application crash; more often this manifests as data corruption. If
someone could give me some direction as to how to include debugging code
in with my distribution, I'd appreciate it...
Gilad
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wxPython-user...@lists.wxwindows.org
> For additional commands, e-mail: wxPython-...@lists.wxwindows.org
>
Gilad Suberri wrote:
> I am having trouble getting the wxEVT_WIZARD_FINISHED to work properly. For
> some reason, when the user presses the finish button, this function never
> gets called. Anybody run into the same thing?
A quick tweak to the demo shows that it is working here.
def fin(self,evt):
self.log.write("OnFinished")
and updated my system to Python 2.2.3 with wxPython 2.4.2.4 on my PC. For
some reason it still doesnt work, but works on my Solaris install of Python
2.2.3 with wxPython2.4.1.2. Am I missing something stupid? Thanks.
Gilad
----- Original Message -----
From: "Robin Dunn" <ro...@alldunn.com>
To: <wxPytho...@lists.wxwindows.org>
No, I tested on Linux before. When I do the same on Windows then I also
don't get the event. I've responded to a similar message in wx-users
with a patch to show the problem. It should get fixed for the next release.