problems with touch under windows
I created a nifty abstraction, a button that changes value and icon based on how long the user holds it down. Works like a charm with the mouse. But with a touchscreen, it doesn't work at all. WIndows seems to start looking for a context menu after a second or so.
Any thoughts how to get around this? If not, a 'touchscreen mode' which overrides this behaviour would be a FR.....
thanks,
-er
pretty sure that's a windows feature? :) ....long press = right click. there's probably a way to turn off touch screen/pen gestures.
it does seem like a bug somewhere that pressing directly on a button would bring up a context menu in a locked patch.
you could try using something like the key or hi object to trigger pressing the button then someone pressing a real or virtual on screen keyboard could hold the key down.
Oh, I'm sure it's a windows feature. But since Mac's don't have a touchscreen feature at all, I'm not going to complain.
It doesn't actually bring up the context window--it just doesn't work.
this is designed to be used without a keyboard... so a kludge would have to include creating the keypress......
--opening a virtual keyboard is WAY not worth it.
Woodslanding, search for a control panel of the touch device to see if there's a way to configure it and disable the "right-click" mode. Touch pads usually have this control panel, maybe the touch screen device has it too.
Bingo!!
Thank you, that's exactly it. There is a checkbox for "click and hold for right click".....
Hopefully that works as expected.
thanks,
-eric
Okay, maybe that's a start.... but mousestate is actually not reporting touches as mousedowns at all. So it's not just a problem with right-click.
I did more testing with mousestate, and discovered if I wiggle my finger a little bit on the touchscreen, I do get a trigger from mousestate. I don't need to do this to trigger any of the max buttons with the touchscreen. Just when I try to use mousestate. Seems like a bug in mousestate.
-eric
I just did a touchscreen test with ubutton, and in the helpfile, the button on page one will not trigger without sliding my finger a little bit. But for whatever reason, the radio button configuration on the second page triggers reliably.
In pictctl, the happy face will not trigger without sliding, but the toggle works fine.
In textbutton, I get reliable triggers--but I can't get a trigger for both mousedown and mouseup. I tired layering 2 buttons, because both mousedown and mouseup modes trigger correctly. But the mousedown is not seen by both.
UButton will give me both triggers, but in "Stay" mode, it does not stay lit while my finger is down--unless I move my finger. I can't find any way in Max to time the length of a press on my touchscreen without moving my finger. So it seems to be some piece of code that is used by all these modules.
Maybe I'll try using mousestate for the mousedown, and textbutton for mouseup. I'll see if that works. Oh nevermind, mousestate has the same problem.
Okay, tried putting the textbutton in toggle mode, but it doesn't change state until I release my finger from the touchscreen, even though it changes state on a mousedown.
So it seems like MAX is not recognizing a touchscreen touch until it is released (or moved).
I'm stumped!!
-e
Just a bump on this.... is there a specific place to put feature requests? I'd like to request this one. I think the touchscreen and max are a great combo, and it would be nice to have proper support for it. I know it can be done, and it doesn't seem like it would be all that difficult. Usine Hollyhock implements it, and it is built on Juce just like Max.
cheers,
-e
Good points!
I suppose one could go either way with mousestate. I am really only looking for mouselike behaviour, but there are a lot of other touchscreen capabilities that could be implemented if you wanted to--scrolling and zooming, etc. I turned them all off in Usine, and used touch just like mousing.
For now, I will find another way.
cheers,
-e
+1 for supporting touchscreen
Yeah, this is really annoying, I can't register a touch until the finger is released or moved slightly, still trying to find a way around it. Many disabled people use touchscreen tablets as communication/ control devices so it would be really useful to properly support them.
+1 here too
I really like to see touchscreen support! Imagine all the cool stuff you could do. Max really should take the next step.
I have said that many times here: A touchscreen and max supporting multi touch would be thousand times greater than mira ... the problem is that the max team is primarily apple and there seems to be no plan of apple to sell a mac book touch or a cinema display with touch support. :-)
Same thing with Cubase! I so much expected multi touch support, the way they upgraded the mixer ... didn't happen with version 8 ... I talked to somneone from steinberg on musikmesse and he told me, they would be mad to release a feature, that was gonna be useless to all Apple customers. Well, that is hpow far this Apple thing has gotten us! IMO Apple is really in the way of progress these days.
FWIW I am running an apple computer live.... but I am running windows. I had hoped to move to an apple OS, but would I lose touch support?
Does even single-touch (mouse emulation) support not work under apple software?