Home > Software engineering >  Mouse messages to other process window, useless, have to send mouse_event? Why is that? How to solve
Mouse messages to other process window, useless, have to send mouse_event? Why is that? How to solve

Time:09-16

My application to other processes, and the mouse message is wm_lbuttondown, found some line, some not, if not, have to send mouse_event, but this requires that the window is the front window, very inconvenient,

Why sometimes not mouse messages, don't want to send mouse_event? Is there a way to make it not the front window can also play a role?

CodePudding user response:

Received message with spy++ captured under the target window, in front of the window is not a case, to see if the target window messages are received

CodePudding user response:

reference 1st floor lx624909677 response:
use spy++ captured under the target window to receive news, in front of the window is not a case, to see if the target window have received message

Do you mean sending wm_lbuttondown message?

CodePudding user response:

Now if I use mouse_event can be normal work target window is like one hand press the mouse,

But use sendmessage sending wm_lbuttondown message are not


But have a trouble with mouse_event is must first set the target window to the front window to also won't be able to work

CodePudding user response:

Try PostMessage distributed to the message queue

CodePudding user response:

http://www.autohotkey.com
Or
CreateDesktop

CodePudding user response:

I want to ask: this is not response wm_lbuttondown message, but it can respond to mouse_event program is how to write? What's the difference?

CodePudding user response:

Keyboard mouse belongs to the input message,
with a focusIf click the child controls, these messages cannot be directly sent to the main form, do you want to control

CodePudding user response:

refer to the second floor screen12 response:
Quote: refer to 1st floor lx624909677 response:

Received message with spy++ captured under the target window, in front of the window is not a case, to see if the target window have received message

Do you mean sending wm_lbuttondown message?

Didn't you say you sometimes messages sent over but actually feel the form is not the response message, so make sure the see if the message is sent in the past

CodePudding user response:

The WM_LBUTTONDOWN, don't forget to send WM_LBUTTONUP

CodePudding user response:

There are two possibilities
1. Take the wrong target window handle. Then sent to where go to, don't know.
2. If the target window, not you write your programs, it is likely the target window on the mouse messages of this kind of special treatment.

CodePudding user response:

A lot of messages is not allowed/cannot across processes,

CodePudding user response:

refer to the eighth floor lx624909677 response:
Quote: refer to the second floor screen12 response:

Quote: refer to 1st floor lx624909677 response:

Received message with spy++ captured under the target window, in front of the window is not a case, to see if the target window have received message

Do you mean sending wm_lbuttondown message?

Didn't you say you sometimes messages sent over but actually feel the form is not the response message, so make sure the message has been sent in the past

Just see the message has been sent to the target window with spy but target program does not handle no response

CodePudding user response:

The
references to the tenth floor xiaohuh421 response:

there are two kinds of possibility1. Take the wrong target window handle. Then sent to where go to, don't know.
2. If the target window, not you write your programs, it is likely the target window on the mouse messages of this kind of special treatment.

It should be

The
references to the tenth floor xiaohuh421 response:

there are two kinds of possibility1. Take the wrong target window handle. Then sent to where go to, don't know.
2. If the target window, not you write your programs, it is likely the target window on the mouse messages of this kind of special treatment.
2

The
references to the tenth floor xiaohuh421 response:

there are two kinds of possibility1. Take the wrong target window handle. Then sent to where go to, don't know.
2. If the target window, not you write your programs, it is likely the target window on the mouse messages of this kind of special treatment.


The
references to the tenth floor xiaohuh421 response:

there are two kinds of possibility1. Take the wrong target window handle. Then sent to where go to, don't know.
2. If the target window, not you write your programs, it is likely the target window on the mouse messages of this kind of special treatment.


Should be the second case because spy tracking to the message sent to a target window


It's difficult for he has a special processing method: how do I let him not front window can also be handled mouse_event can but requirement is the front window

CodePudding user response:

I just want to ask does not handle wm_lbuttondown message but response mouse_event program how to write?

CodePudding user response:

refer to 12 floor screen12 reply:
Quote: refer to the eighth floor lx624909677 response:

Quote: refer to the second floor screen12 response:

Quote: refer to 1st floor lx624909677 response:

Received message with spy++ captured under the target window, in front of the window is not a case, to see if the target window have received message

Do you mean sending wm_lbuttondown message?

Didn't you say you sometimes messages sent over but actually feel the form is not the response message, so make sure the message has been sent in the past

Just see the message has been sent to the target window with spy but I can't response target program does not handle

The window to receive direct physical built according to the message and send the past as yourself?

CodePudding user response:

reference 15 floor lx624909677 response:
Quote: refer to 12 floor screen12 reply:

Quote: refer to the eighth floor lx624909677 response:

Quote: refer to the second floor screen12 response:

Quote: refer to 1st floor lx624909677 response:

Received message with spy++ captured under the target window, in front of the window is not a case, to see if the target window have received message

Do you mean sending wm_lbuttondown message?

Didn't you say you sometimes messages sent over but actually feel the form is not the response message, so make sure the message has been sent in the past

Just see the message has been sent to the target window with spy but I can't response target program does not handle

The window to receive direct physical built according to the message and send the past as yourself?

The same

CodePudding user response:

Just tried a virtual desktop software, found that if the program runs in the virtual desktop, if the current display is not a virtual desktop, then mouse_event is not to send the message the message to the corresponding window, only to the virtual desktop display, mouse messages can be sent to the window,nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull
  • Related