3 ms·
$1 Unistroke Recognizer
- 4ndrewl 3y agoReminds me of the old Palm Pilot input mechanism, Graffiti https://en.m.wikipedia.org/wiki/Graffiti_(Palm_OS) https://en.m.wikipedia.org/wiki/Graffiti_(Palm_OS)
- fxtentacle 3y agoI cannot seem to draw a right curly brace in a way that it recognizes it. It's almost as if the recognition was rotation-invariant because I sometimes get v or check as a false positive for }.
- thaumasiotes 3y agoI can draw a } that it will recognize, but it takes special effort. A natural } that no human would have difficulty with tends to be "recognized" as a ] instead. Even when there is a VERY prominent center point protruding from the shape. I also have trouble with the registered "arrow" shape - if you overshoot the point when you're doing the return from the top half of the arrowhead, you'll get recognized as a random non-arrow shape. The "x" does not match the way I would naturally write an x, and it really highlights the fact that many common shapes are not drawn in a single stroke. (Also a problem for the arrow, as well as the "delete", which is clearly supposed to be visually identical to "x". It will be a problem for a large number of important characters that don't exist in the demo, such as A, t, and +.) Between that and the fact that it has so much trouble recognizing }, which is visually distinctive and is naturally drawn in a single stroke, this doesn't seem like an algorithm you'd want to let users interact with. Adding a single example of a } as drawn by me more or less removed that recognition problem. It introduced a symmetric problem where obviously squared-off ] was recognized as }. Adding the perfectly squared ] as an example of "right square bracket" reintroduced the inability to recognize very obvious }. I suspect this is not a solvable problem without switching to a more effective algorithm.
- swiftcoder 3y agoThe whole family of algorithms (including the multistroke variants) suffer from this issue. They are very clever, and maybe suitable if your set of templates are sufficiently distinct, but they don't deal at all well with similar shapes
- bagels 3y agoIt does not seem to recognize 'left handed' versions of the gestures. Try to draw a curly brace from the bottom up, or the star in a counterclockwise pattern.
- cushpush 3y agoStroke-order dependent?
- smokracek 3y agoI noticed this too. Draw a left curly brace from the bottom up, it calls it a right curly brace, and the reverse is true as well.
- jldugger 3y agoThat's intentional, afaict. The circle in the diagram represents the stroke start point.
- verdverm 3y agoThis is a family of recognizers. I used the $P or P+, which do much better for your case, I was drawing boxes
- ceautery 3y agoIt rotates the path so that the first point is to the right of center mass. See https://makezine.com/article/maker-news/gesture-recognition-for-javasc/ https://makezine.com/article/maker-news/gesture-recognition-...
- bagels 3y agoThis behavior is independent of starting point. Drawing the star counterclockwise demonstrates.
- pvg 3y agoOngoing discussion at https://news.ycombinator.com/item?id=38249891 https://news.ycombinator.com/item?id=38249891
- dang 3y agoThanks! Macroexpanded: Ship Shape - https://news.ycombinator.com/item?id=38249214 https://news.ycombinator.com/item?id=38249214 - Nov 2023 (49 comments) Also, in case of interest: $1 Unistroke Recognizer (2007) - https://news.ycombinator.com/item?id=27046822 https://news.ycombinator.com/item?id=27046822 - May 2021 (65 comments) $1 Unistroke Recognizer - https://news.ycombinator.com/item?id=10245928 https://news.ycombinator.com/item?id=10245928 - Sept 2015 (41 comments)
- have_faith 3y agoI used the Flash version of this when I was in university to make some funky art installations. Funny to see it pop up over a decade later.
- Minor49er 3y agoIs there more information about the installation available? Sounds like it would be a cool project
- thomastjeffery 3y agoSo the name of the thing is "$1"... How stupid do we have to be with names??!?!
- userbinator 3y agoWas expecting cheap hardware, then looked through the whole page trying to figure out what this had to do with money.
- shadedtriangle 3y agoIt's because the algorithm is easy to implement and efficient in terms of compute usage to match a gesture. It's a "cheap and easy" recognizer, a $1 recognizer. The name has spawned a whole host of similarly named papers which you can see on their "impact" page https://depts.washington.edu/acelab/proj/dollar/impact.html https://depts.washington.edu/acelab/proj/dollar/impact.html.
- thomastjeffery 3y agoThat doesn't help the ambiguity at all. You have to know contextually that the dollar sign and the digit are part of the name before you can read any sentence that contains the name. That guarantees that you will be confused at least once!
- lelandfe 3y agoHere is that terrible confusion: “Is that a price or a name? Ah, a name”
- thomastjeffery 3y agoThen you continue: "You can't use $1 to..." The ambiguity never leaves. It's an absolutely unnecessary overhead that demands more than any other name I have ever encountered.
- 3y ago
- acoward113472 3y agoso.. that character in the upper right... is that suppose to be recognized as a '3' or as boobies?
- qwertox 3y agoIt doesn't support straight lines (1D lines), like a single stroke right. According to the PDF you need to implement your own bounding box analysis for this. I was reading about it this week because I needed a gesture recognition library but haven't found anything else. BetterTouchTool uses this library.