One tiny and one crippling. Yes, it was the right version but
I goofed up on the second 'y/u/v' assignment, can't believe I did
something *that* dumb.
The effect was cool though - diagonal black lines across the screen.
The inequality gaffe wouldn't hurt too much - pretty hard to get
exactly get the '=' condition. I saw that too and was wondering
to myself if I should change it.
Actually, this was crippling: the first set of loops goto'd out when
num_dark reaches pixel_thresh. So num_dark <= pixel_thresh always,
which meant that the check before the second set of loops always
goto'd right to the end. I found this after a radius of 128 had no
effect!
Also, as it stands it doesn't actually report the number of dark
pixels; it reports num_dark from the first set of loops, which clips
at pixel_thresh.
Dan
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
