Open some dialog boxes and the mouse cursor moves to one of the dialog buttons

[**Developer**]

Open some dialog boxes and the mouse cursor moves to one of the dialog
buttons.
I'd like to implement that .
Is that simply something I have to program, i.e. figure out where I want the
cursor and move it.
Or does DotNet help somehow?

Thanks

[Scott Swigart]

Here you go.
Create a form with a button on it, and then paste in the following code:

Public Declare Function SetCursorPos Lib "user32" (ByVal X As Integer,
ByVal Y As Integer) As Long
Public Declare Function ClientToScreen Lib "user32" (ByVal hWnd As
IntPtr, ByRef point As POINT) As Boolean

Private Sub Form1_Load(ByVa l sender As System.Object, ByVal e As
System.EventArg s) Handles MyBase.Load
Dim p As New POINT
p.x = Button1.Left + (Button1.Width / 2)
p.y = Button1.Top + (Button1.Height / 2)
ClientToScreen( Me.Handle, p)
SetCursorPos(p. x, p.y)
End Sub

- Scott Swigart

P.S. Moving the mouse for the user is generally considered a no-no.

"**Develope r**" wrote:

Open some dialog boxes and the mouse cursor moves to one of the dialog
buttons.
I'd like to implement that .
Is that simply something I have to program, i.e. figure out where I want the
cursor and move it.
Or does DotNet help somehow?

Thanks

[Dennis]

In Windows XP, you can set the options for the mouse to jump to the default
button when a form is opened I think.
--
Dennis in Houston
"Scott Swigart" wrote:

Here you go.
Create a form with a button on it, and then paste in the following code:

Public Declare Function SetCursorPos Lib "user32" (ByVal X As Integer,
ByVal Y As Integer) As Long
Public Declare Function ClientToScreen Lib "user32" (ByVal hWnd As
IntPtr, ByRef point As POINT) As Boolean

Private Sub Form1_Load(ByVa l sender As System.Object, ByVal e As
System.EventArg s) Handles MyBase.Load
Dim p As New POINT
p.x = Button1.Left + (Button1.Width / 2)
p.y = Button1.Top + (Button1.Height / 2)
ClientToScreen( Me.Handle, p)
SetCursorPos(p. x, p.y)
End Sub

- Scott Swigart

P.S. Moving the mouse for the user is generally considered a no-no.

"**Develope r**" wrote:

Open some dialog boxes and the mouse cursor moves to one of the dialog
buttons.
I'd like to implement that .
Is that simply something I have to program, i.e. figure out where I want the
cursor and move it.
Or does DotNet help somehow?

Thanks

[Dragon]

SetCursorPos is actually Boolean, not Long.

Roman

"Scott Swigart" <sc***@swigartc onsulting.com> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ ×
ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ:
news:83******** *************** ***********@mic rosoft.com...

Here you go.
Create a form with a button on it, and then paste in the following code:
Public Declare Function SetCursorPos Lib "user32" (ByVal X As Integer, ByVal Y As Integer) As Long
Public Declare Function ClientToScreen Lib "user32" (ByVal hWnd As
IntPtr, ByRef point As POINT) As Boolean

Private Sub Form1_Load(ByVa l sender As System.Object, ByVal e As
System.EventArg s) Handles MyBase.Load
Dim p As New POINT
p.x = Button1.Left + (Button1.Width / 2)
p.y = Button1.Top + (Button1.Height / 2)
ClientToScreen( Me.Handle, p)
SetCursorPos(p. x, p.y)
End Sub

- Scott Swigart

P.S. Moving the mouse for the user is generally considered a no-no.

"**Develope r**" wrote:

Open some dialog boxes and the mouse cursor moves to one of the dialog buttons.
I'd like to implement that .
Is that simply something I have to program, i.e. figure out where I want the cursor and move it.
Or does DotNet help somehow?

Thanks

[Jay B. Harlow [MVP - Outlook]]

**Developer**,
First I would like to strongly suggest you don't implement it. As a number
of users find it *rude* for a program to move their mouse for them.
Here is a version of Scott's code that does not use P/Invoke (Declare
statements).

Private Sub Form1_Load(ByVa l sender As System.Object, ByVal e As
System.EventArg s) Handles MyBase.Load
Dim p As New Point
p.X = Button1.Left + (Button1.Width \ 2)
p.Y = Button1.Top + (Button1.Height \ 2)
Cursor.Position = Me.PointToScree n(p)
End Sub

Both Win32 APIs are already exposed in the Framework, no need to use
Declare...

Hope this helps
Jay

" **Developer**" <RE************ *@a-znet.com> wrote in message
news:eR******** ******@TK2MSFTN GP14.phx.gbl...
| Open some dialog boxes and the mouse cursor moves to one of the dialog
| buttons.
| I'd like to implement that .
| Is that simply something I have to program, i.e. figure out where I want
the
| cursor and move it.
| Or does DotNet help somehow?
|
| Thanks
|
|

[Larry Lard]

**Developer** wrote:

Open some dialog boxes and the mouse cursor moves to one of the dialog
buttons.
I'd like to implement that .
Is that simply something I have to program, i.e. figure out where I want the
cursor and move it.
Or does DotNet help somehow?

As others have said, you shoudl carefully consider if you really want
your application to dictate this behaviour.

Since Windows 2000 (I believe), users have had the ability to set this
behaviour on a *global* level (eg in XP it is in Control Panel | Mouse
| Pointer Options | Snap To), and by implication if they have *not* set
this option, it means that they *do not* want this behaviour. For one
application to behave in this way regardless of the global setting
would I think be seen as extremely unfriendly.

--
Larry Lard
Replies to group please

[**Developer**]

Thanks to all.

As to the suggestions against it I note that MS does it often.
For example, Open Notepad/File/Open
If there is a way for the user to turn it on/off I'd sure like to know how
to read his setting.
How can I check the user settings?

At first I didn't like it but then got used to it.

Something else I don't like is sometimes I want to delete one character or
move one character left and the insertion point moves to the start of the
line. I can't remember exactly what it is but I know when it has happened I
did not like it. Wish I could shut that feature off.
Thanks again
" **Developer**" <RE************ *@a-znet.com> wrote in message
news:eR******** ******@TK2MSFTN GP14.phx.gbl...

Open some dialog boxes and the mouse cursor moves to one of the dialog
buttons.
I'd like to implement that .
Is that simply something I have to program, i.e. figure out where I want
the cursor and move it.
Or does DotNet help somehow?

Thanks

[**Developer**]

Larry is correct in XP it can be set in controlpanel.
Then it doesn't have to be implemented.
Simply declare the default button and the rest is automatic.
I didn't try but I'd guess it also works with MessageBox if the default
button is specified.

" **Developer**" <RE************ *@a-znet.com> wrote in message
news:eR******** ******@TK2MSFTN GP14.phx.gbl...

Open some dialog boxes and the mouse cursor moves to one of the dialog
buttons.
I'd like to implement that .
Is that simply something I have to program, i.e. figure out where I want
the cursor and move it.
Or does DotNet help somehow?

Thanks

[Jay B. Harlow [MVP - Outlook]]

Larry,
Thanks for the reminder: XP Pro has a similar option available as does
Windows Server 2003.

Hope this helps
Jay
"Larry Lard" <la*******@hotm ail.com> wrote in message
news:11******** **************@ g44g2000cwa.goo glegroups.com.. .
|
| **Developer** wrote:
| > Open some dialog boxes and the mouse cursor moves to one of the dialog
| > buttons.
| > I'd like to implement that .
| > Is that simply something I have to program, i.e. figure out where I want
the
| > cursor and move it.
| > Or does DotNet help somehow?
|
| As others have said, you shoudl carefully consider if you really want
| your application to dictate this behaviour.
|
| Since Windows 2000 (I believe), users have had the ability to set this
| behaviour on a *global* level (eg in XP it is in Control Panel | Mouse
|| Pointer Options | Snap To), and by implication if they have *not* set
| this option, it means that they *do not* want this behaviour. For one
| application to behave in this way regardless of the global setting
| would I think be seen as extremely unfriendly.
|
| --
| Larry Lard
| Replies to group please
|