Re: [python-win32] Shell extension debugging

2009-06-29 Thread Gertjan Klein
Mario Alejandro Vilas Jerez wrote: >Did you try killing all instances of explorer.exe instead of rebooting? That >might do the trick and it's faster. I've checked with Process Explorer, but even if I use the Windows Explorer setting "Launch folder windows in a separate process" there is still onl

Re: [python-win32] Shell extension debugging

2009-06-29 Thread Tim Roberts
Gertjan Klein wrote: > I am trying to write a shell context menu handler, based on the example > I found in Lib\site-packages\win32comext\shell\demos\servers. My > ultimate goal is to have a single top-level menu, with a number of > submenu entries determined at runtime. (I want to make a launcher

Re: [python-win32] Shell extension debugging

2009-06-29 Thread Tim Roberts
Gertjan Klein wrote: > I've checked with Process Explorer, but even if I use the Windows > Explorer setting "Launch folder windows in a separate process" there is > still only one explorer.exe visible, which is at the root of everything > I have open. I wouldn't want to kill that one... > That'

Re: [python-win32] Shell extension debugging

2009-06-29 Thread Kevin Horn
Just an aside on restarting explorer... In case explorer doesn't restart automatically, you can easily start it up again manually from the task manager (which you should have open from killing the process). File->NewTask, then type explorer. I'm sure this isn't news to most people here, but I'm

Re: [python-win32] Shell extension debugging

2009-06-29 Thread Gertjan Klein
Kevin Horn wrote: >In case explorer doesn't restart automatically, you can easily start it up >again manually from the task manager (which you should have open from >killing the process). Thanks, that tip just saved me! If I kill explorer.exe from task manager, my taskbar and desktop icons disapp

Re: [python-win32] Shell extension debugging

2009-06-29 Thread Gertjan Klein
Tim Roberts wrote: >Gertjan Klein wrote: >>(I want to make a launcher for >> command prompts, so I can open a command prompt at a given directory >> with appropriate settings for python: path, C compiler, etc.) > >Interesting! I wrote basically that same extension (in C++) about 5 >years ago. I

Re: [python-win32] Shell extension debugging

2009-06-29 Thread Tim Roberts
Gertjan Klein wrote: > It doesn't over here, but another poster has shown me how to circumvent > this. If this is the only way to do that I will; there is no way to tell > PyWin32 to reload the extension? (I know reloading in Python is tough, > I'm expecting a "no" here. ;-)) > I was going to r

Re: [python-win32] Shell extension debugging

2009-06-29 Thread Randy Syring
Gertjan Klein wrote: Tim Roberts wrote: Gertjan Klein wrote: (I want to make a launcher for command prompts, so I can open a command prompt at a given directory with appropriate settings for python: path, C compiler, etc.) Maybe I am missing something, but I use the "Open Comma

Re: [python-win32] Shell extension debugging

2009-06-29 Thread Vernon Cole
On Mon, Jun 29, 2009 at 12:17 PM, Gertjan Klein wrote: > Tim Roberts wrote: > > >Gertjan Klein wrote: > >> 2) I see print statements in the source code, but I have no idea where > >> they go; I checked the event log, but they are not there. Are they > >> logged anywhere? If not, why are they the