I hope to detect whether the screen is the mouse to Click and perform the Click event, or strikes by the touch screen, so, when the user clicks the mouse, jump out of the smaller menu, when a user touch screen, display the larger menu button, the VB6 what should be the difference? Thank you very much!

CodePudding user response:

Application level should be impossible to judge, because touch screen on the system is a similar to the mouse input device.
Estimates that you have to start from such as drive. But it is difficult.
Compromise: to a number of menu, whether the mouse or touch screen are all the same

CodePudding user response:

There is no difference,
Hardware can at the same time with a touch screen, mouse, software is the mouse operation,
Can add a start the welcome screen, let the user choose a size two sets of style,

CodePudding user response:

Just make a touch screen of c + + project
Seeing you is what's chip of the touchscreen
Or you can try use eGalaxTouch drive, this is the generic driver touch screen, regardless of manufacturer

Drive there is a library of secondary development, can make your program to receive touch information and won't touch information directly into the mouse
Use RegisterTPNotifyMessage development kit inside the function, register window receiving information

RegisterTPNotifyMessage

DWORD WINAPI

RegisterTPNotifyMessage (

HANDLE hFile,

The HWND HWND,

UINT imsg

);

RegisterTPNotifyMessage registers a notification message for touch event so that the window can receive the message whenever the touch event happens.

The Parameters

HFile

Device handle obtained by CreateDevice

HWnd

The Target window to receive the caller defined message when touch the event happened.

Imsg

Caller defined message.

Remark

The Target window will receive The caller defined message whenever The touchscreen

Was touched. With this caller defined message, wParam is the touch proximity state, LOWORD (lParam) is X the coordination, and HIWORD (lParam) is Y coordination. The coordination data is always scaled to 0 ~ 65535 for the driver before version 5.0.1.5310. When working With driver version 5.0.1.5310 or later, the coordination data is not scaled. The home, the value range depends on the AD resolution to the in wParam.

The window can receive The caller defined message only when The device thread was started with StartDeviceThread.

Driver, version 5.0.1.5310 or later, supports multiple ADC resolution, multi - user, pressure. To information can be obtained in wParam

WParam is a 32 bits of data, as described below

B31 B24 B23 B16

Player ID
Pressure
B15 ~ B8
0
Z
M
0
0
AD1
AD0
The Status


Z=1, B16 ~ B23 is 8 bits pressure information

M=1, B24 ~ B31 is 8 bits of multi - user player ID

AD1: AD0=resolution of the coordination data.

AD1:0-0 at AD0=11 bits resolution

AD1: AD0=1-0 12 bits resolution

AD1: AD0=1-0 13 bits resolution

AD1: AD0=1:1 14 bits resolution

See Also

RegisterDeviceRemovalHook

CodePudding user response:

As for this development kit can support vb I don't know
But it need to use MFC library operation