Closed Sotatek-HuyTran9 closed 3 days ago
Hi, do you see "Touchpad exists and is registered" on the app? Do you see the fingers coordinates appearing on the app like on the readme:
What is your displayed event speed?
Also, can you check that in the Three Fingers Drag, the "Enable three fingers mouse move" option is enabled?
Touchpad: Registered Event speed: 6ms Enable three fingers mouse move: Enabled
Please help to resolved :)
same problem here :/
Hi, I published a new release that allows to record the app logs and to save the log file from the Other settings pane. Can you update TFDOW and enable the logging, restart the app, try to do a three-fingers drag, stop the logging, and upload the file here?
Download the v2.0.2 here or on the Microsoft Store.
Logs_ThreeFingerDragOnWindows.txt This is the log file
Looks like your touchpad reports an empty touchpad contacts list half the time. I can try to fix that issue by ignoring the empty touchpad contacts reports. I couldn't identify any three fingers drag on the log file. The log size is limited to 10,000 lines, can you try again to record logs just trying a single three finger drag, and stopping the logging right after it. Can you also tell me what CPU architecture you have so I'll be able to build a custom version for you, trying to fix the bug.
Logs_ThreeFingerDragOnWindows.txt Here you go Please lemme know if I missed anything
Thank's, it is strange as there is no persistent report for three fingers at the same time, even removing the empty reports. I will make a new build for you soon, but the bug is most likely due to the library emoacht/RawInput.Touchpad that I am using (see https://github.com/emoacht/RawInput.Touchpad/issues/1).
I released a new version of TFDOW that ignores empty contacts reports. It might change the dragging behavior you are having, and the logs too. Can you check it?
Download the v2.0.3 here or on the Microsoft Store.
I just released a new version of TFDOW that should fix some bugs regarding the touchpad raw input parsing for touchpads that send reports "sequentially". It might fix this issue.
Can you try again on the v2.0.5 (Microsoft Store). If you still have issues, you can share again the log file.
version v2.0.5.0 The current version still has this issue [Uploading Logs_ThreeFingerDragOnWindows.txt…]()
You sent the message too fast, the log file you were trying to upload hasn't had the time to upload. Can you send it again?
I fully understand that many new versions may not be as stable. However, is it possible to implement a feature that allows us to disable automatic updates? This would enable us to adhere to a stable version and avoid disruptions to our familiar workflow.
Hi @kit-zeason, You can install ThreeFingersDragOnWindows from GitHub releases if you do not want to have automatic updates.
@bigdou-x, your logs files reveals the same issue as in #63 and #66: the raw hid reports correctly a contact count of three, but there is actually only one contact information available. I will try to fix this soon.
Okay, thank you for your hard work
The v2.0.5 indeed broke the TFD for the touchpads that send each contact as individual raw hid reports.
I fixed the bug and tried to make a new parsing algorithm that should work with all touchpads, even if I can’t test it. The v2.0.6 is on its way to being certified by the Microsoft Store!
I verified it, it's solved.
I disabled the "Tap twice and drag to multi-select" option, and enable the "Enable three fingers drag" in the app, but it's not working.
Please help to support, thank you