extensions
extensions copied to clipboard
TurboWarp
New extension: Multi Touch
Multi-touch extension (to replace sensing+'s)
x: x position y: y position dx: change of x position compared to previous frame dy: change of y position compared to previous frame sx: avg speed x of finger in a second sy: avg speed y of finger in a second duration: time since finger press force (some devices only): force of finger press
Tested on:
- iOS device
- android device
Not tested on:
- laptop with touchscreen
WHY DO ALL THE GOOD EXTENSIONS HAVE THAT ONE FAILED THAT STOPS THEM FROM GETTING MERGED?! I really needed that extension and didn't want to have to manually load it unsandboxed...
WHY DO ALL THE GOOD EXTENSIONS HAVE THAT ONE FAILED THAT STOPS THEM FROM GETTING MERGED?! I really needed that extension and didn't want to have to manually load it unsandboxed...
the "one failed" is just formatting and it gets fixed during a merge session. there won't be any merges until a week or so from now.
I will add a block <hovered by any fingers?>
And hopefully it will merge within a month lol
I will add a block <hovered by any fingers?>
And hopefully it will merge within a month lol
Can you add blocks like 'touching a finger' or 'current finger touching' like in sensing+
Seriously hope this gets merged relatively quickly
Yeah we need this (me specifically)
(or someone can just ask garbomuffin to merge it in discord like i did for the soundexpanded thing)
What's the issue with sensing plus? No-one seems to like it.
We do like it it's just @David-Orangemoon forgot to add MultiTouch WebAPI for iOS or something idk (sensing+ doesn't work for iOS)
What's the issue with sensing plus? No-one seems to like it.
We do like it it's just @David-Orangemoon forgot to add MultiTouch WebAPI for iOS or something idk (sensing+ doesn't work for iOS)
I support this extension if they somehow figured out the cryptic safari touch api (which doesn't have features it says it has) if so then I fully support it.
@Skyhigh173 Ill test it on my chromebook. The only thing that prevent me from testing sensing+'s mobile touch was the lack of ios devices in my area.
@Skyhigh173 Ill test it on my chromebook. The only thing that prevent me from testing sensing+'s mobile touch was the lack of ios devices in my area.
You mean you'll update Sensing+ to work for iOS?!? :D
@Skyhigh173 Ill test it on my chromebook. The only thing that prevent me from testing sensing+'s mobile touch was the lack of ios devices in my area.
You mean you'll update Sensing+ to work for iOS?!? :D
no this exists now.
Why update sensing+ if it's already a big mess, it's best for the extension to start being split up.
The one thing I'm not sure about here is how there is a "number of fingers" and "number of fingers ID" -- at the very least the names need to be clarified and ideally a docs page added. Are people expected to just loop up to ID and use "finger ( ) exists?"?
The one thing I'm not sure about here is how there is a "number of fingers" and "number of fingers ID" -- at the very least the names need to be clarified and ideally a docs page added. Are people expected to just loop up to ID and use "finger ( ) exists?"?
What if: finger 1 pressed finger 2 pressed finger 1 released
are finger 2 supposed to be finger 1 now?
No it should still be finger 2. The question is how to make that clear to people who don't know how this works
I think sensing+ has the same "quirk" so honestly we can probably just not worry about it too much
No it should still be finger 2. The question is how to make that clear to people who don't know how this works
I think we have to add a document to solve this problem
And also there's a problem: If user tap in a very short period of time and release (let's say < 0.03s), there will have a chance that it can't be detected by the scripts This is a serious problem if you are trying to make (mobile) rhythm games
I think the extension would need to maintain its own touch identifier mapping to hide all details like that. People will write scripst like "wait until < not < finger 1 pressed? > >" and we should make it work reliably
should I test on my Chromebook for the category "laptop with touch screen"?
should I test on my Chromebook for the category "laptop with touch screen"?
yes
should I test on my Chromebook for the category "laptop with touch screen"?
yes
seems to work correctly for the most part, but I noticed something.
lets say you put 2 fingers down. if you let go of finger 1 and not 2, the project freezes until you lift finger 2.
tried this both with and without the extension, its definetely a problem with the extension itself.
should I test on my Chromebook for the category "laptop with touch screen"?
yes
seems to work correctly for the most part, but I noticed something.
lets say you put 2 fingers down. if you let go of finger 1 and not 2, the project freezes until you lift finger 2.
What do you mean by "freeze"?
should I test on my Chromebook for the category "laptop with touch screen"?
yes
seems to work correctly for the most part, but I noticed something. lets say you put 2 fingers down. if you let go of finger 1 and not 2, the project freezes until you lift finger 2.
What do you mean by "freeze"?
no visual updates whatsoever