Hi MOJO,
Yes, jsut as Tom stated, calling AttachThreadInp ut with SetForegroundWi ndow
will definitely bring your window to foreground. But this is not a
recommended design on Windows, normally, you should just call
SetForegroundWi ndow. If the Windows finds that the end user is busy doing
operations, it will flash your window with blue colors in the taskbar. This
is a more recommended behavior than using AttachThreadInp ut.
Furthermore, SetForegroundWi ndow Win32 API is encapsulated in the .Net
Framework Form.Activate() method.
Public Sub Activate()
IntSecurity.Mod ifyFocus.Demand
If (MyBase.Visible AndAlso MyBase.IsHandle Created) Then
If Me.IsMdiChild Then
Me.MdiParentInt ernal.MdiClient .SendMessage(&H 222,
MyBase.Handle, 0)
Else
UnsafeNativeMet hods.SetForegro undWindow(New HandleRef(Me,
MyBase.Handle))
End If
End If
End Sub
So you may call me.Activate() to bring the form to the foreground.
Hope this helps.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
=============== =============== =============== =====
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
=============== =============== =============== =====
This posting is provided "AS IS" with no warranties, and confers no rights.