LiveCode Forums.

I have an app designed for Mac and Windows. I use the mouseDown and mouseUp in a button to execute different commands. It works fine when using the mouse or the touchpad on a PC laptop, but doesn't respond correctly when using the touchScreen. The mouseDown command triggers when I release the button on the touchScreen. (It's as if it's backwards ??) The mouseUp command is never sent.

I tried adding touchStart and touchEnd to the script but to no avail.

Any advice is much appreciated...

That used to be a problem on mobile too but it was fixed. If I remember right, mouseDown is sent by the OS but mouseUp is artificially generated. I'm not sure why it doesn't work on the touchscreen. Maybe LC doesn't recognize it as a touch device because it's running a desktop OS?

It used to work fine way back in versions 5.x.x 6.x.x and maybe some of the 7s that I used to use for a (Windows) desktop game in kiosk mode with a touch screen to control the points of a train track. That was only using mouseUp IIRC, not mouseDown and certainly never touchStart and touchEnd.
I can't say if and when it might have stopped working, I have no touchscreen I can try it with on newer versions.

Most touch screens deliver messages to the OS in the same way touchpads do.

Have you seen any anomalous behavior with other apps? Or with a touchpad or mouse?

What is the make and model of the device?

Hi Richard. Here is a simple example stack. It works fine with the mouse and touchpad but not with the touchScreen. I tried it on a 15" HP envy laptop with touchscreen. I had a report that it doesn't work on Dell touchscreen either..

thanks,
Richard

Thank you for posting the stack, but the only touch devices I have here right now are iOS and Android, so I won't be able to test the stack on Windows.

I asked for the make and model of the devices in question to see if users in those forums have found anomalies with other software that relies on standard OS messaging. Checking those forums would seem a useful diagnostic move.

I've scoured the forums but haven't found anything very useful. However, I did discover that if I move my finger ever so slightly on the button, the mouseDown function triggers properly and when I release it the mouseUp function also works.

I tried setting different properties of the button (sharedHilite, traversal, focusBorder etc.) but it made no difference.

My discovery leads me to believe that there may be a workaround but I'm at a bit of a loss...

thanks for any insight.

I too do not have a windows system with a touch screen to test this on, but sounds like it may be worth a bug report?