Blob Detected X: 0.063366 Y : 0.008768 Area : -0.000095

wat are these deciaml point and -ve values ?? ... how do they specify the location of point and area covered by a touch ?? .... wats the unit ... and how can they be converted to pixels ???

(srry for a noob query .... )

X,Y ranges from 0-1. Multiply X by your screen resolution-x and Y with your screen resolution y. So for a 1024x768 resolution ... you should be doing x *= 1024; and y *=768;

ohhhk !! ... thnx

and wat bout the area then ?? ..... the values r in -ve !!

also, when u include the brightness/contrast filter and move the sliders, the corresponding values stored in config.xml are in decimal point and +ve or -ve ..... wats the conversion for tht ???

area values shouldn’t be negative. I think that isn’t fixed cause no one’s actually using it for their applications ? You should just use the absolute values and ignore the signs, that’s what i’m doing.

I dont think you should worry about the config.xml values too much. as long as once you calibrate your system and it works well. You shouldn’t have to bother about converting those values anyways.

ya ... its working alright ...
but the thing is, i need to know ..... plz if someone can ???

RGLoFMI - 25 April 2008 04:28 PM

X,Y ranges from 0-1. Multiply X by your screen resolution-x and Y with your screen resolution y. So for a 1024x768 resolution ... you should be doing x *= 1024; and y *=768;

Are you sure this is true? Should it not be compared to the camera-resolution rather than screen-resolution?

entity - 28 April 2008 02:28 PM

RGLoFMI - 25 April 2008 04:28 PM

X,Y ranges from 0-1. Multiply X by your screen resolution-x and Y with your screen resolution y. So for a 1024x768 resolution ... you should be doing x *= 1024; and y *=768;

Are you sure this is true? Should it not be compared to the camera-resolution rather than screen-resolution?

It is the screen resolution

then I must admit I’m a bit confused about a problem I have in my DI-setup. It’s like everything moves in a grid. Movement of objects - no matter how slow - only updates after the movement is 2-3 pixel compared to the screen resolution.

I’ve made a thread about it here…

http://nuigroup.com/forums/viewthread/1728/