We are experiencing an issue after updating to Build 228. About 80% of the time a touch screen's touch functionality (as opposed to utilizing the mouse) is utilized, the console appears to be waiting ~2 seconds and then registering a second click in the exact location of the initial touch point. For example, if a Direct Select is touched after 2 seconds the same direct select will register a second click. In attempting to edit a Macro, when EDIT is touched after about 2 seconds it will register DONE since the Done functionality replaces the Edit functionality. It is actively preventing programming utilizing touch screen functionality.
I might have seen something similar. Do you see that constantly or is it something that starts at some point?
There doesn't seem to be any rhyme or reason to it. It seem pretty consistent in terms of how long before the second click occurs, but there doesn't seem to be any action that causes the double clicking to start or resolve itself. Does that make sense/help?
I'm on a Ti Enhanced with 2 external touchscreens, but I've seen the phantom touch issue only on the internal screens so far.
What is your hardware situation?
Maybe this helps ETC track down the issue...
We are using a Ti and are also only experiencing it on the Internal Touchscreens so far.
Thank you both for your report. We'll start looking into this.
If you could upload logfiles here that would help the investigation. Bonus points if you could press [Displays]&[Record] when you see this happen. This will insert a mark into the logfiles so the event is easier to find in the logs.
i uploaded my logs. one example of this happening is at 2021 08 13 21:16:06.
We did a bit of system cleaning and I can no longer reproduce the issue. We manually deleted several files that were no longer needed on the console and then performed a "Deep Clear" in System Maintenance from the shell. I have not been able to register a double click on any touchscreens (internal or external) at this point.
We haven't been able to reproduce this. SStheatreLD could you still upload your logs and indicate what time and date it happened, please?
I wasn't able to get any logs during the sessions it was happening and we have updated to the new beta version at this point. I'm assuming that clears the logs? We will make sure to grab logs if we experience any strangeness in the future. Sorry about that!
Logs persist through software updates and Deep Clears, so there is probably still some valuable data there we would like to look at.