<

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x

Moving a Form by Clicking Anywhere in the Window

Published on
13,018 Points
6,718 Views
3 Endorsements
Last Modified:
Approved
Community Pick
Normally a window is moved by clicking on the caption bar and dragging. You may want your user to be able to move borderless forms or move a form by clicking anywhere in the form without the limitation to the caption bar. There are many ways to do it. Two of the most commonly-seen solutions are:

Standard Three-Event Handling
Handle the mousedown, mouseup, mousemove events. You can set a "dragging now" flag in mousedown and record the initial mouse coordinates as the start point.   In mousemove event, calculate the delta between the current mouse position and the start point. Set the window's new location using this delta as deviation value so the window will follow the mouse movement.  Finally, set the "dragging now" flag to false to turn off the dragging.

It's a functional technique. But you need to handle three events and use flags and variables to accomplish the work.

Re-target Form-Dragging Events
A simpler way is to intercept the message loop of a form and re-target the mouse events hitting the client area and send them to the caption bar, as shown in the following code snippet:
private const int WM_NCHITTEST = 0x0084;
    private const int HTCLIENT = 1;
    private const int HTCAPTION = 2;
    protected override void WndProc(ref Message m)
    {
      base.WndProc(ref m);
      switch (m.Msg)
      {
        case WM_NCHITTEST:
          if (m.Result == (IntPtr)HTCLIENT)
          {
            m.Result = (IntPtr)HTCAPTION;
          }
          break;
      }
    }

Open in new window

If we have 20 forms and if we want them to have the similar behavior, using "copy &  paste" to get the above sequence into each one of the 20 files would be nasty.  A clean way is to create a derived class from Windows.Form:
public class InterceptProcForm:Form

Open in new window

and put the above codes in this class. Then you replace the default base class Form with InterceptProcForm for all your forms:    
public partial class Form1 : InterceptProcForm

Open in new window

No more need to change your source codes -- all the forms are following your mouse now.

Handling User-Controls
The question now comes up:  "What if a form is completely covered by a user control?" Now the message in WndProc() that originated from controls will be redirected to the control's caption which is meaningless to a control and the form will stay there quietly.

The solution is to handle the mousemove event and flood it to its owner form, as shown in this link: C# borderless form move by usercontrol.

Once again we need to take code reuse into consideration. In the above link, a generic type FormDragPanel is used and user panels can inherit from it to move the underlying form. It's an improvement but not enough. There are tens (if not tons) of various types of user control; for some of them we may want the dragging capability and for others we would just keep them as it is. A common type derived from UserControl is not feasible because C# does not support multiple inheritance. A quick thought is to create a separate FormDragXxxx for each type of control: FormDragLabel, FormDragPictureBox, FormDragProgressBar, etc. But your work does not end here. You need to touch the Designer-generated code and add an event chain in your form for each of the controls.

Inspired by Marcel, here's a kind of "adapter" pattern I've used to resolve the scenario. Simply add the following class FormDragBase in your project.
public class FormDragBase : System.Windows.Forms.Form
    {
        public const int WM_NCLBUTTONDOWN = 0xA1;
        public const int HT_CAPTION = 0x2;

        [DllImportAttribute("user32.dll")]
        public static extern int SendMessage(IntPtr hWnd, int Msg, int wParam, int lParam);
        [DllImportAttribute("user32.dll")]
        public static extern bool ReleaseCapture();

        protected override void OnMouseMove(System.Windows.Forms.MouseEventArgs e)
        {
            base.OnMouseMove(e);

            if (e.Button == System.Windows.Forms.MouseButtons.Left)
            {
                if (WindowState == FormWindowState.Normal)
                {
                    ReleaseCapture();
                    SendMessage(Handle, WM_NCLBUTTONDOWN, HT_CAPTION, 0);
                }
            }
        }

        public void AddDraggingControl(System.Windows.Forms.Control theControl)
        {
            theControl.MouseMove += new System.Windows.Forms.MouseEventHandler(OnControlMouseMove);
        }

        private void OnControlMouseMove(object sender, MouseEventArgs e)
        {
            if (e.Button == System.Windows.Forms.MouseButtons.Left)
            {
                if (WindowState == FormWindowState.Normal)
                {
                    ReleaseCapture();
                    SendMessage(Handle, WM_NCLBUTTONDOWN, HT_CAPTION, 0);
                }
            }
        }
    }

Open in new window

Derive your own form from this base class, then add the controls for which you want them to be transferable; for instance:
public partial class Form1 : FormDragBase
    {
        public Form1()
        {
            InitializeComponent();
            AddDraggingControl(this.label1);
            AddDraggingControl(this.pictureBox1);
            AddDraggingControl(this.progressBar1);
        }
    }

Open in new window

So... There you go.  Simple and easy!
3
Comment
Author:trestan
  • 3
  • 2
  • 2
7 Comments
LVL 12

Expert Comment

by:starlite551
Or Simple Just Add this :........
Point refPoint;
protected override void OnMouseDown(object sender, MouseEventArgs e)
{
     refPoint = new Point(e.X,e.Y);  
}

protected override void OnMouseMove(object sender, MouseEventArgs e)
        {
            if (e.Button == MouseButtons.Left)
            {
                this.Left += e.X - p.X;
                this.Top += e.Y - p.Y;
            }
        }

Open in new window

0
LVL 8

Author Comment

by:trestan
It's similiar to the first one introduced in the article. However, what if the form is covered by a control?
0
LVL 14

Expert Comment

by:systan
GOod article.
0
Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

LVL 14

Expert Comment

by:systan
I voted yes;
But can you just
AddDraggingControlToAll_Object(); ?  You don't know too?
0
LVL 8

Author Comment

by:trestan
Not sure what exactly you want to do.
0
LVL 12

Expert Comment

by:starlite551
You can always check whether the focus of Mouse Pointer is on a Control Or On the Form itself while moving this way :
Point p;
        protected override void OnMouseDown(MouseEventArgs e)
        {
            if (this.Bounds.Contains(Cursor.Position))
            {
                p = new Point(e.X, e.Y);    
            }
            
        }
        protected override void OnMouseMove(MouseEventArgs e)
        {
            if (e.Button == MouseButtons.Left)
            {
                Left += e.X - p.X;
                Top += e.Y - p.Y;
            }
        }

Open in new window

0
LVL 8

Author Comment

by:trestan
Yes. You are right. Then you need to add the above code to every control to be transferable.
0

Featured Post

Become a CompTIA Certified Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

Join & Write a Comment

Did you know PowerShell can save you time with SaaS platforms? Simply leverage RESTfulAPIs to build your own PowerShell modules. These will kill repetitive tickets and tabs, using the command Invoke-RestMethod. Tune into this webinar to learn how…
A query can call a function, and a function can call Excel, even though we are in Access. This is Part 2, and steps you through the VBA that "wraps" Excel functionality so we can use its worksheet functions in Access. The declaration statement de…

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month