Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm no shape recognition expert, but here's how I might approach the problem.</p> <p>First, while displaying the user's path as freehand, secretly accumulate a list of point (x, y) samples along with times. You can get both facts from your drag events, wrap them into a simple model object, and pile those up in a mutable array.</p> <p>You probably want to take the samples fairly frequently—say, every 0.1 seconds. Another possibility would be to start out <em>really</em> frequent, maybe every 0.05 seconds, and watch how long the user drags; if they drag longer than some amount of time, then lower the sample frequency (and drop any samples that would've been missed) to something like 0.2 seconds.</p> <p>(And don't take my numbers for gospel, because I just pulled them out of my hat. Experiment and find better values.)</p> <p>Second, analyze the samples.</p> <p>You'll want to derive two facts. First, the center of the shape, which (IIRC) should just be the average of all of the points. Second, the average radius of each sample from that center.</p> <p>If, as @user1118321 guessed, you want to support polygons, then the rest of the analysis consists of making that decision: whether the user wants to draw a circle or a polygon. You can look at the samples as a polygon to start with to make that determination.</p> <p>There are several criteria you can use:</p> <ul> <li>Time: If the user hovers for longer at some points than others (which, if samples are at a constant interval, will appear as a cluster of consecutive samples near each other in space), those may be corners. You should make your corner threshold small so that the user can do this unconsciously, rather than having to deliberately pause at each corner.</li> <li>Angle: A circle will have roughly the same angle from one sample to the next all the way around. A polygon will have several angles joined by straight line segments; the angles are the corners. For a regular polygon (the circle to an irregular polygon's ellipse), the corner angles should all be roughly the same; an irregular polygon will have different corner angles.</li> <li>Interval: A regular polygon's corners will be equal space apart within the angular dimension, and the radius will be constant. An irregular polygon will have irregular angular intervals and/or a non-constant radius.</li> </ul> <p>The third and final step is to create the shape, centered upon the previously-determined center point, with the previously-determined radius.</p> <p>No guarantees that anything I've said above will work or be efficient, but I hope it at least gets you on the right track—and please, if anyone who knows more about shape recognition than me (which is a very low bar) sees this, feel free to post a comment or your own answer.</p>
    singulars
    1. This table or related slice is empty.
    1. PODraw a perfect circle from user's touch
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USPeter Hosey
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. CO+1 Hi, thanks for the input. Very informative. Likewise, I wish that the iOS/"shape recognition" superman will somehow see this post and enlighten us further.
      singulars
      1. PO
      1. USUnheilig
    2. CO@Unheilig: Good idea. Done.
      singulars
      1. PO
      1. USPeter Hosey
    3. COYour algorithm sounds good. I would add a check on how far the user's path diverged from a perfect circle/polygon. (For example, percent mean square deviation.) If it's too large, the user might not want the ideal shape. For a skilled doodler, the cutoff would be smaller than for a sloppy doodler. Having this would allow the program to give artistic freedom to artists but lots of help to beginners.
      singulars
      1. PO
      1. USdmm
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload