C#

Programm3r wrote:

So, my question: how can I develop / alter the event(s) (which runs on a separate thread that the main) to not make use of the above technique, and still be able to send / set data to the GUI controls?

N a v a n e e t h wrote:

BTW, why do you want to do this?

The only programmers that are better C# programmers, are those who look like this ->

Programm3r
My Blog: ^_^

[DllImport("user32.dll")]
        static extern IntPtr SetParent(IntPtr hWndChild, IntPtr hWndNewParent);

        [DllImport("user32.dll", CharSet = CharSet.Auto)]
        private static extern int SendMessage(IntPtr hWnd, int wMsg, IntPtr wParam, IntPtr lParam);

        private const int WM_MOUSEMOVE = 0x200;
        private const int WM_LBUTTONDOWN = 0x201;
        private void button2_Click(object sender, EventArgs e)
        {
            SendMessage(axe.Handle, WM_LBUTTONDOWN, IntPtr.Zero, IntPtr.Zero);
            SendMessage(axe.Handle, WM_MOUSEMOVE, IntPtr.Zero, IntPtr.Zero);
}

protected override void WndProc(ref Message m)
{
    Debug.WriteLine(m.ToString()); // writes to the output window of visual studio when debugging a debugging build
    base.WndProc(ref m);
}

jamesjk wrote:

but nothing special happened...
no event in the message receiving control was fired..
am I missing anything ?