On Tue, Jul 8, 2008 at 7:29 AM, Mark Hammond <[EMAIL PROTECTED]> wrote:
>
>> The debugging trace suggests that IsMemberOf are called after
>> GetOverlayInfo, which itself is called when Explorer starts up.
>
> That is correct - GetOverlayInfo is called just once per process IIUC.
> Having this fun
On Tue, Jul 8, 2008 at 8:24 AM, Tim Golden <[EMAIL PROTECTED]> wrote:
> Mark Hammond wrote:
>>
>>
>>>
>>> The debugging trace suggests that IsMemberOf are called after
>>> GetOverlayInfo, which itself is called when Explorer starts up.
>>
>> That is correct - GetOverlayInfo is called just once per
On Tue, Jul 8, 2008 at 7:08 AM, Mark Hammond <[EMAIL PROTECTED]> wrote:
>> I am trying to provide a way for user to [totally] disable the overlay
>> extension, and enable them later if they want, without having to go
>> through the pain to remove the shell extension from windows registry.
>
> Why i
Mark Hammond wrote:
The debugging trace suggests that IsMemberOf are called after
GetOverlayInfo, which itself is called when Explorer starts up.
That is correct - GetOverlayInfo is called just once per process IIUC.
Having this function fail should prevent your IsMemberOf being called - but
> The debugging trace suggests that IsMemberOf are called after
> GetOverlayInfo, which itself is called when Explorer starts up.
That is correct - GetOverlayInfo is called just once per process IIUC.
Having this function fail should prevent your IsMemberOf being called - but
once it has been s
> I am trying to provide a way for user to [totally] disable the overlay
> extension, and enable them later if they want, without having to go
> through the pain to remove the shell extension from windows registry.
Why is removal from the registry a pain?
> > If you want something specific to you
On Mon, Jul 7, 2008 at 11:03 AM, Tim Golden <[EMAIL PROTECTED]> wrote:
> TK Soh wrote:
>>
>> I'd like to know what's the 'proper' way to stop a pythonwin's overlay
>> shell extension from kicking in. I've not been able find much
>> documentation on this, particularly the return values of
>> GetOver
On Mon, Jul 7, 2008 at 7:14 AM, Mark Hammond <[EMAIL PROTECTED]> wrote:
>> I'd like to know what's the 'proper' way to stop a pythonwin's overlay
>> shell extension from kicking in. I've not been able find much
>> documentation on this, particularly the return values of
>> GetOverlayInfo() function
TK Soh wrote:
I'd like to know what's the 'proper' way to stop a pythonwin's overlay
shell extension from kicking in. I've not been able find much
documentation on this, particularly the return values of
GetOverlayInfo() function. Based on sample that I've found, the
GetOverlayInfo() function ret
> I'd like to know what's the 'proper' way to stop a pythonwin's overlay
> shell extension from kicking in. I've not been able find much
> documentation on this, particularly the return values of
> GetOverlayInfo() function. Based on sample that I've found, the
> GetOverlayInfo() function returns a
You wrote:
>
>... Based on sample that I've found, the
>GetOverlayInfo() function returns a tuple of (icon_path, 0,
>shellcon.ISIOI_ICONFILE), and it's not clear to me what the '0' is
>representing.
Icon files can contain multiple icons. The 0 is the ordinal of the icon that
should be used -- th
I'd like to know what's the 'proper' way to stop a pythonwin's overlay
shell extension from kicking in. I've not been able find much
documentation on this, particularly the return values of
GetOverlayInfo() function. Based on sample that I've found, the
GetOverlayInfo() function returns a tuple of
12 matches
Mail list logo
