From: Karl E. Peterson on
on 6/27/2010, Leo supposed :
> MikeD pretended :
>> "Leo" <ttdhead(a)gmail.com> wrote...
>>> I tried looking at the MS example and it confuses me especially after
>>> reading the MSDN doco for FindText. I have been thinking abou going about
>>> the operation using Karl's HookXP subclassing method to catch the
>>> FINDMSGSTRING Message. Would that be an acceptable method?
>>> http://support.microsoft.com/kb/267939 is the MS example
>>
>> What do you find confusing? I mean, the KB article provides you sample
>> code. Have you tried running it and studying it?
>
> I got it running, but it goes in a totally different dirrection to the msdn
> docs probably so as not to go into subclassing though.

That is a really bizarre approach! They're still subclassing, but
they're just hooking one of the buttons on the dialog. That presents
all sorts of other hurdles, and necessitates hard-coding the dialog
elements. <shudder> I'd definitely advocate for doing it the MSDN way,
not the KB way! In fact, this might make a cool sample. I'll have to
see if I have time to work it in. :-)

--
..NET: It's About Trust!
http://vfred.mvps.org


From: Leo on
After serious thinking Karl E. Peterson wrote :
> on 6/27/2010, Leo supposed :
>> MikeD pretended :
>>> "Leo" <ttdhead(a)gmail.com> wrote...
>>>> I tried looking at the MS example and it confuses me especially after
>>>> reading the MSDN doco for FindText. I have been thinking abou going about
>>>> the operation using Karl's HookXP subclassing method to catch the
>>>> FINDMSGSTRING Message. Would that be an acceptable method?
>>>> http://support.microsoft.com/kb/267939 is the MS example
>>>
>>> What do you find confusing? I mean, the KB article provides you sample
>>> code. Have you tried running it and studying it?
>>
>> I got it running, but it goes in a totally different dirrection to the msdn
>> docs probably so as not to go into subclassing though.
>
> That is a really bizarre approach! They're still subclassing, but they're
> just hooking one of the buttons on the dialog. That presents all sorts of
> other hurdles, and necessitates hard-coding the dialog elements. <shudder>
> I'd definitely advocate for doing it the MSDN way, not the KB way! In fact,
> this might make a cool sample. I'll have to see if I have time to work it
> in. :-)

I was thinking similar things especially if I want to display the
up/down radio buttons. Could I still use there method but listen for
the message MSDN says to listen for?

--
ClassicVB Users Regroup! comp.lang.basic.visual.misc
Free usenet access at http://www.eternal-september.org


From: Karl E. Peterson on
Leo brought next idea :
> After serious thinking Karl E. Peterson wrote :
>> on 6/27/2010, Leo supposed :
>>> MikeD pretended :
>>>> "Leo" <ttdhead(a)gmail.com> wrote...
>>>>> I tried looking at the MS example and it confuses me especially after
>>>>> reading the MSDN doco for FindText. I have been thinking abou going
>>>>> about the operation using Karl's HookXP subclassing method to catch the
>>>>> FINDMSGSTRING Message. Would that be an acceptable method?
>>>>> http://support.microsoft.com/kb/267939 is the MS example
>>>>
>>>> What do you find confusing? I mean, the KB article provides you sample
>>>> code. Have you tried running it and studying it?
>>>
>>> I got it running, but it goes in a totally different dirrection to the
>>> msdn docs probably so as not to go into subclassing though.
>>
>> That is a really bizarre approach! They're still subclassing, but they're
>> just hooking one of the buttons on the dialog. That presents all sorts of
>> other hurdles, and necessitates hard-coding the dialog elements. <shudder>
>> I'd definitely advocate for doing it the MSDN way, not the KB way! In
>> fact, this might make a cool sample. I'll have to see if I have time to
>> work it in. :-)
>
> I was thinking similar things especially if I want to display the up/down
> radio buttons. Could I still use there method but listen for the message MSDN
> says to listen for?

The FINDMSGSTRING message? If you hook your own window, and pass that
as the parent to the FindText call, that'd be the one to watch for,
yeah.

http://msdn.microsoft.com/en-us/library/ms646872%28v=VS.85%29.aspx

--
..NET: It's About Trust!
http://vfred.mvps.org


From: Karl E. Peterson on
on 6/26/2010, Leo supposed :
> I tried looking at the MS example and it confuses me especially after reading
> the MSDN doco for FindText. I have been thinking abou going about the
> operation using Karl's HookXP subclassing method to catch the FINDMSGSTRING
> Message. Would that be an acceptable method?
> http://support.microsoft.com/kb/267939 is the MS example

Hey Leo! See "FindReplace - Bruce said it couldn't be done...", which
I just posted. :-)

--
..NET: It's About Trust!
http://vfred.mvps.org


From: Leo on
Karl E. Peterson was thinking very hard :
> on 6/26/2010, Leo supposed :
>> I tried looking at the MS example and it confuses me especially after
>> reading the MSDN doco for FindText. I have been thinking abou going about
>> the operation using Karl's HookXP subclassing method to catch the
>> FINDMSGSTRING Message. Would that be an acceptable method?
>> http://support.microsoft.com/kb/267939 is the MS example
>
> Hey Leo! See "FindReplace - Bruce said it couldn't be done...", which I just
> posted. :-)

Just looking at it now. I'm glad I set myself up a personal SVN server
to allow myself to keep the woring code clean ;-)

--
ClassicVB Users Regroup! comp.lang.basic.visual.misc
Free usenet access at http://www.eternal-september.org


First  |  Prev  | 
Pages: 1 2
Prev: ListView Hit test
Next: Java's "readInt" to VB6