jit.suckah question/bug??

Oct 10, 2008 at 10:20pm

jit.suckah question/bug??

so I am using suckah for the first time in a long while and I am probably just misunderstanding something…

I expected the following behaviour:
place the jit.suckah over anything and a mouse-down will give the the rgb value of that pixel. If I move my mouse inside suckah while it is still down, the values get updated. If I move outside the suckah perimeter, I shouldn’t get any more values.

This is what I get:
As long as I click on the suckah and don’t let go, my values get updated!! Even when I leave the Max window and drag over something on my desktop!!!

Is that the normal behaviour???
Am I making sense??

here is a quick test patch (for both Max 5 and 4.6). I only want to be able to track the color within the rectangle and nothing else.

Thanks for any insight.

– Pasted Max Patch, click to expand. –

#P user suckah 55 168 100 100;
#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#P message 124 132 30 196617 read;
#P hidden newex 55 371 54 196617 prepend 0;
#P newex 56 397 135 196617 jit.matrix bar 4 char 16 16;
#P user jit.pwindow 55 422 217 176 0 1 0 0 1 0;
#P newex 56 131 63 196617 jit.qt.movie;
#P newex 279 165 111 196617 jit.lcd 4 char 320 240;
#P message 427 123 180 196617 brgb 0 0 0 , frgb 0 255 0 , pensize 4 4;
#P message 279 124 143 196617 framerect 0 0 150 150 , bang;
#P newex 279 98 57 196617 qmetro 33;
#P toggle 279 66 15 0;
#P message 56 98 131 196617 read colorwheel.jpeg , bang;
#P newex 56 45 48 196617 loadbang;
#P user jit.pwindow 53 166 210 171 0 1 0 0 1 0;
#P connect 12 0 8 0;
#P fasten 8 0 7 0 61 156 284 156;
#P connect 10 0 9 0;
#P hidden connect 11 0 10 0;
#P hidden connect 13 0 11 0;
#P hidden connect 7 0 0 0;
#P fasten 4 0 8 0 284 120 61 120;
#P connect 4 0 5 0;
#P connect 2 0 8 0;
#P fasten 6 0 7 0 432 151 284 151;
#P connect 5 0 7 0;
#P connect 1 0 2 0;
#P fasten 1 0 3 0 61 64 284 64;
#P fasten 1 0 6 0 61 92 432 92;
#P connect 3 0 4 0;
#P window clipboard copycount 14;

#40276
Dec 8, 2008 at 11:46am

This is just how suckah works. You could use a mousestate object to test if the mouse has left the boundaries of the object (and use js to get those boundaries) and filter.

Or you could wait for 5.0.6, coming soon, which adds the @boundmode attribute to the suckah object to handle this for you.

Jeremy

#142311
Dec 9, 2008 at 8:37pm

awesome, thanks.

#142312

You must be logged in to reply to this topic.