Re: Cursor within dialog bounds

From:

"Tom Serface" <tom.nospam@camaswood.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Thu, 7 Jun 2007 08:18:05 -0700

Message-ID:

<uuvgRcRqHHA.4536@TK2MSFTNGP05.phx.gbl>

I see others have advised you to check the WM_MOVE message, but you will
also want to check if the dialog get resized (if you allow that).

Tom

"Yoavo" <yoav@cimatron.co.il> wrote in message
news:uwuhbGOqHHA.1208@TK2MSFTNGP02.phx.gbl...

The ClipCursor API works ok, but I have the following problem:
After the user moves the dialog, the cursor does not stay in the dialog
area...
Note that I call ClipCursor in OnInitDialog.

"Tom Serface" <tom.nospam@camaswood.com> wrote in message
news:OaAIRNHqHHA.1216@TK2MSFTNGP03.phx.gbl...

I agree. I think that's what I was trying to say :o) Of course, the OP
probably knows his target better than we do. However, I feel it's part of
the act of community to give our opinions just in case OP hasn't
considered some implication.

Tom

"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
news:knod63tjbns67qrt2f5f9mv1hctacsrumq@4ax.com...

Generally, the only reason to clip the cursor is druing some drag
operation when the mouse
button is being held down. Clipping it when the modeless dialog is up
is one of those
techniques usually classified as "user hostile"
joe

On Wed, 6 Jun 2007 08:38:26 -0700, "Tom Serface"
<tom.nospam@camaswood.com> wrote:

I see that two others have given you the answer, but I have to pose the
question... if you want to keep the cursor inside the dialog why not
make it
a modal dialog? That would make it much easier to handle and preclude
the
parent window from interacting in other ways (like using the keyboard).

I can understand the need to clip the cursor on occasion (like during a
drag
and drop operation), but you'll want to be careful not to keep users
from
doing other things on their system that they may want to do while your
program is running.

Tom