> On 5/23/07, Mark Hammond <[EMAIL PROTECTED]> wrote:
> > I think the problem is likely related to the "main frame"
> issue quoted below.
> > I suggest you debug what the app's "main frame" is at any
> given point in
> > time, and confirming the value is still appropriate.
>
> I tried putting th
On 5/23/07, Mark Hammond <[EMAIL PROTECTED]> wrote:
> I think the problem is likely related to the "main frame" issue quoted below.
> I suggest you debug what the app's "main frame" is at any given point in
> time, and confirming the value is still appropriate.
I tried putting this statement in th
On 5/23/07, Mark Hammond <[EMAIL PROTECTED]> wrote:
> I think the problem is likely related to the "main frame" issue quoted below.
> I suggest you debug what the app's "main frame" is at any given point in
> time, and confirming the value is still appropriate.
Being new to pywin32, I'm not sur
I think the problem is likely related to the "main frame" issue quoted below.
I suggest you debug what the app's "main frame" is at any given point in time,
and confirming the value is still appropriate.
Mark
> On 5/15/07, Mark Hammond <[EMAIL PROTECTED]> wrote:
> > > > This is the magic of MF
On 5/15/07, Mark Hammond <[EMAIL PROTECTED]> wrote:
> > > This is the magic of MFC - if no parent is specified, the
> > "main window" for
> > > the application is automatically used.
> > >
> >
> > Isn't that the issue, then? He's writing a dialog to plug in to
> > Explorer, and every time he runs,
> > This is the magic of MFC - if no parent is specified, the
> "main window" for
> > the application is automatically used.
> >
>
> Isn't that the issue, then? He's writing a dialog to plug in to
> Explorer, and every time he runs, there's a different "main window".
> MFC gets its concept of a "m
Mark Hammond wrote:
>>> I don't see the parent being passed into the dialogs in pywin32's
>>> sample code. Is this going to be a problem?
>>>
>> Well, in looking at the code, I don't even see a way to
>> specify one, so
>> this seems to have been a rat hole.
>>
>> I'm mildly surprised by tha
> > I don't see the parent being passed into the dialogs in pywin32's
> > sample code. Is this going to be a problem?
>
> Well, in looking at the code, I don't even see a way to
> specify one, so
> this seems to have been a rat hole.
>
> I'm mildly surprised by that. The CreateDialog APIs all take
TK Soh wrote:
>
> Actually I didn't specify any parent at all:
>
> class MyDialog(Dialog):
>def __init__(self, title=None, tmpl=None):
>self.title = title
>if tmpl is None:
>tmpl = dlg_template()
>Dialog.__init__(self, tmpl)
>
> I don't see the parent being p
On 5/15/07, Tim Roberts <[EMAIL PROTECTED]> wrote:
> TK Soh wrote:
> >
> > Thanks for the info, but I'm not sure about Platform SDK. I started
> > doing this windows thing directly with python32.
> >
> > The HookMessage is called in OnInitDialog(), so I presumed is called
> > every time a new dialo
TK Soh wrote:
>
> Thanks for the info, but I'm not sure about Platform SDK. I started
> doing this windows thing directly with python32.
>
> The HookMessage is called in OnInitDialog(), so I presumed is called
> every time a new dialog is created (I'm very new to windows
> programming):
Yes, it is
On 5/15/07, Tim Roberts <[EMAIL PROTECTED]> wrote:
> TK Soh wrote:
> > The hooks are working, so I guess PYWIN_WITH_WINDOWPROC support has
> > indeed been compiled into ActivePython. The only problem now is the
> > strange behavior when sometime the hooks don't get triggered. Any
> > suggestion on
TK Soh wrote:
> The hooks are working, so I guess PYWIN_WITH_WINDOWPROC support has
> indeed been compiled into ActivePython. The only problem now is the
> strange behavior when sometime the hooks don't get triggered. Any
> suggestion on workaround?
>
Where do you call HookWindow? Are you call
On 5/15/07, Niki Spahiev <[EMAIL PROTECTED]> wrote:
> >> In order to hook more messages (e.g. WM_SIZE) you must recompile pywin32
> >> with PYWIN_WITH_WINDOWPROC defined
> >
> > I'm confused. The hooks appeared to work fine, though only in the
> > dialog opened from the specific explorer window as
>> In order to hook more messages (e.g. WM_SIZE) you must recompile pywin32
>> with PYWIN_WITH_WINDOWPROC defined
>
> I'm confused. The hooks appeared to work fine, though only in the
> dialog opened from the specific explorer window as I described
> earlier. I've tried WM_SIZE, WM_ACTIVATE, etc.
On 5/15/07, Niki Spahiev <[EMAIL PROTECTED]> wrote:
> TK Soh wrote:
> > Greeting.
> >
> > I built a custom dialog which would be resized by a handler connected
> > with HookMessage() to win32con.WM_SIZE. The dialogs are actually
> > called from the shell extension's context menu. Every seemed to wo
TK Soh wrote:
> Greeting.
>
> I built a custom dialog which would be resized by a handler connected
> with HookMessage() to win32con.WM_SIZE. The dialogs are actually
> called from the shell extension's context menu. Every seemed to work
> well at first.
>
> The I noticed the resize handler is on
Greeting.
I built a custom dialog which would be resized by a handler connected
with HookMessage() to win32con.WM_SIZE. The dialogs are actually
called from the shell extension's context menu. Every seemed to work
well at first.
The I noticed the resize handler is only called on the dialogs that
18 matches
Mail list logo
