Re: Atl Property Sheet stays empty
- From: "Alexander Nickolov" <agnickolov@xxxxxxxx>
- Date: Wed, 6 Jul 2005 09:56:20 -0700
I suspect we are talking different languages... The way I read
the documentation for IShellPropSheetExt, it knows nothing
about OLE property pages, it only understands regular
PROPSHEETPAGE structures used with the regular property
sheet API CreatePropertySheetPage(). If you want framework
support, ATL doesn't provide it. You need WTL.
http://sourceforge.net/projects/wtl
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@xxxxxxxx
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"Egbert Nierop (MVP for IIS)" <egbert_nierop@xxxxxxxxxxxxxx> wrote in
message news:eTfe1IagFHA.2444@xxxxxxxxxxxxxxxxxxxxxxx
> "Alexander Nickolov" <agnickolov@xxxxxxxx> wrote in message
> news:O5BGJlYgFHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
>> Hmm, can't really help you much here...Why would you want
>> to create a dialog in the first place? You are supposed to be
>> using property pages instead of dialogs.
>
> I got lost..
> Why do you think I'm trying to create a Dialog?
> The Dialog I meantion implements IPropertyPageImpl.
>
> Please see my other posting about the very strange hidden windows. My code
> works but it looks as if SetWindowText is set on a *clone* of the control
> that I want to manipulate.
>
> Why are the controls cloned?
>
>
>> --
>> =====================================
>> Alexander Nickolov
>> Microsoft MVP [VC], MCSD
>> email: agnickolov@xxxxxxxx
>> MVP VC FAQ: http://www.mvps.org/vcfaq
>> =====================================
>>
>> "Egbert Nierop (MVP for IIS)" <egbert_nierop@xxxxxxxxxxxxxx> wrote in
>> message news:u4qVjbwfFHA.3316@xxxxxxxxxxxxxxxxxxxxxxx
>>> "Alexander Nickolov" <agnickolov@xxxxxxxx> wrote in message
>>> news:OfawsGmfFHA.2752@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Reading through the documentation for IShellPropSheetExt::
>>>> AddPages, you are supposed to call CreatePropertySheetPage
>>>> and then the callback function passed as your first argument
>>>> with the returned handle and your second argument. You
>>>> are not supposed to create a dialog here.
>>>
>>> You might be very right here. The dialog could be created in the
>>> DialogProc when the message WM_INITDIALOG is posted. It simplifies
>>> programming as well. However, the MFC sample really creates a Dialog in
>>> the AddPages method. Worse, they have all the code to initialize stuff
>>> in that event. That's the reason, why I hardly can reuse that code.
>>>
>>> (MFC sample code was here...
>>>
>>> PlatSDK\Samples\netds\adsi\samples\DSUI\userext\userproppage)
>>>
>>>
>>> I'll let you know the results ! (if you're interested).
>>
>>
>
.
- References:
- Re: Atl Property Sheet stays empty
- From: Egbert Nierop \(MVP for IIS\)
- Re: Atl Property Sheet stays empty
- From: Alexander Nickolov
- Re: Atl Property Sheet stays empty
- From: Egbert Nierop \(MVP for IIS\)
- Re: Atl Property Sheet stays empty
- From: Alexander Nickolov
- Re: Atl Property Sheet stays empty
- From: Egbert Nierop \(MVP for IIS\)
- Re: Atl Property Sheet stays empty
- Prev by Date: IShellExecuteHook::Execute()
- Next by Date: COM Clustering?
- Previous by thread: Re: Atl Property Sheet stays empty
- Next by thread: Re: Atl Property Sheet stays empty
- Index(es):
Relevant Pages
|