[instaviz-users] Recog 1.0.1 -- use this instead

[Glen Low]

Daniel

On 06/10/2008, at 10:14 AM, Daniel Grobe Sachs wrote:

> 1. In my opinion, the multistroke setting doesn't interfere at all  
> with
> the responsiveness of the interface, and I find it easier to draw
> certain shapes with it on, so I recommend the multistroke variant in
> the final variant.

OK. I will experiment with the multistroke variant in the actual  
Instaviz app, to see if it goes with the flow of the app.

> 2. Small circles are recognized as taps.

There has to be some basic threshold here, since I need to recognize  
pure taps as well -- e.g. selecting an existing shape as opposed to  
drawing a new shape. The threshold is set by the system, and while I  
can override it, I'd rather not make the recognition more sensitive  
than typical usage on the iPhone.

> 3. If I draw something that has not-quite-straight lines (for  
> instance,
> using my thumb one-handed while holding the device), the recognizer
> decides that shapes with sharp corners and bowed lines is an
> ellipse/circle rather than a rectangle/square. This is true even
> if the shape is drawn with multiple strokes. I think that squares
> and circles should be summarily excluded if a corner is seen or
> multiple strokes are used, because they simply don't make any sense
> in that context.

Interesting. You can try taking some screenshots and emailing them to  
me -- hold the Home button and press the top button, the screen will  
flash and save it to your Photos roll; navigate there and then email  
the right one to me.

Were you drawing incomplete or overlapped rectangles or squares?

> 4. The recognizer seems to be a bit confused about squares versus
> rectangles, and ellipses vs circles, in cases where the shape is
> somewhat but not hugely different in height and width. I've seen ---
> or at least I think I've seen, though it's hard to be sure --- cases
> where a a shape that has a larger difference between length and width
> will be recognized as a square, and a smaller difference recognized as
> a rectangle. I think that the thing to do here is to simply attempt to
> recognize the shape as a square/rectangle or ellipse/circle then  
> apply a
> hard cutoff on the difference between height and width to  
> subcategorize
> as square or rectangular; this will at least avoid the odd cases where
> shapes are recognized inconsistently. We'd probably need to do some
> training runs to get this threshold adjusted correctly; I'd suggest
> updating recog to provide a button to indicate when it got it "wrong"
> and feeding this back to your server for analysis.

Again was it incomplete or overlapped rectangles or squares? A couple  
of screenshots would be useful.
>




Cheers, Glen Low


---
pixelglow software | simply brilliant stuff
www.pixelglow.com
aim: pixglen