Re: CreateDialog and sending a WM_NOTIFY from it

On 11/17/2024 11:26 AM, R.Wieser wrote:

> I Think I explained it in full in my first post: I want/need to get the
> "window ID" of a(n owned) dialog (the IDD_SETTINGS one that was used as an
> argument to CreateDialog).  Thats all.  No more, no less.
> 
> So no, there is nothing academic about it ... unless you are trying to "meta
> problem" the whole thing - which is not something I'm willing to participate
> in.
> 
> Any talk about *the example* of what I currently wanted to use it for is, to
> me, wasted time.  You see, that notification already works (before I posted
> my question here), even thoughI had to hard-code the "window ID".
> 

     And also everyone else's wasted time. The standard way to discuss
these things is to explain what you're trying to do and post your code.
With you it's always a confusing riddle. "I want to figure out the best
way to mount this plaque with bull horns on the wall." But you neglect
to mention that you haven't caught the bull yet and the mounting is set
to be 15 feet high on concrete. Meanwhile, people have been led to believe
that you're asking about picture hanging hardware.

    Then someone generously offers what they know about picture
hanging hardware and you criticize them. "You fool! Did I say I want
picture hanging hardware? Show me where I said that. Show me
where I even so much as said 'hook'. Ah, why do I have to suffer fools?!"