Dear Jaewon,

I'm having trouble controlling the cursor on the subject screen in touch mode. I'm using a Wacom touchpad device. The cursor moves only on the control screen and not on the subject screen.

Could you please assist me with this issue?

Wacom is basically another computer, like a tablet. For the subject screen, you need a monitor controlled by your MonkeyLogic computer.

We are using a Wacom device as a touchpad (note: it does not have a screen). You can find more details about our Wacom device here: [india-iws.in].

Here’s our setup:

We have two monitors—one serves as the control screen, and the other is the subject screen. The Wacom device is used to perform tasks on the subject screen and is mapped specifically to it.

The issue arises when running the task: the touch tracker only detects movement on the control screen instead of the subject screen.

Okay. I thought you were talking about a Wacom display model.

Are you running the task in the simulation mode, by any chance?

I also tested it in simulation mode, but it still isn't working.

Could you implement cursor feedback on the subject screen based on the cursor feedback from the control screen? I believe this could resolve the issue.

Reason: Currently, the cursor feedback is visible only on the control screen.

It seems that you programmed it as the touchscreen input, didn't you? Your device is a replacement of the mouse, not the touchscreen, so you should program it as such.

The mouse input is supported only in Timing Script v2 (a.k.a., the scene framework). Use mouse_, instead of touch_. And do not forget to check on "Mouse / Key" in the [Other device settings].

You're absolutely right. I'm currently using mouse mode, but unlike touch mode, mouse mode isn't mapped to the object position on the subject's screen.

For instance, when I touch the center of the Wacom pad, the cursor should immediately appear at the center of the screen, not off in a corner.

I have an idea. In the current Touch mode, the cursor feedback is only displayed on the control screen. If you could enable the cursor feedback to appear on the subject screen simultaneously, it would enhance functionality.

This would require mapping the cursor feedback to both screens effectively.

Could you provide any updates regarding my earlier email?

Please be patient. I cannot just modify existing functions without considering how the changes will affect those who are already using them.

Download the package again and try it. You need to add the following command to your timing file.
https://monkeylogic.nimh.nih.gov/docs_RuntimeFunctions.html#showtouch

showtouch(true);  % v1
touch_.showcursor(true);  % v2