Click-drag problem :(

I'm now making a click too much gadget. And I've experienced this click-drag problem a lot. I tried to put llSetStatus(STATUS_BLOCK_GRAB,TRUE); into the root prim. But it was fruitless. Should I have put it into all prims? All prims except root are buttons and should be movable. Should I have changed their status everytime?

The description for STATUS_BLOCK_GRAB seems to be misleading:
If value is TRUE, object can't be grabbed and physically dragged. See llDetectedGrab.

Then further down the page it says this:
* STATUS_GRAB only affects the prim the llSetStatus function is in; child prims in linked objects won't be affected.

So yes, I would try placing it in each prim. Whether or not these settings are persistent, I am not sure. I can only assume they would be.

Hello Gaz, my neigbor

Thank you. I'll try to put it into every prim. But do you think this prim-drift problem is physical relevant?

EDIT:
Oh, let me make myself clear, the click-drag make all linked prim move even though I just click a button which is a child prim.

If you want to click-drag just one child prim (button), you'll have to do some black magic (i love black magic). I.e. you need to unlink the prim first (upon touch event), then make it link back up once released. Or... You make the prim-that-was-touched report to the rest of the link set that it's in "moving" mode, and every other prim corrects it's position to the original position (using llSetPos) based on a timer (say every 0.1 seconds). Either option is less than ideal of course, but you can't accomplish what you are trying to do, you either move all prims in a link set or none by default (without using black magic).

And yes, you need to set STATUS_BLOCK_GRAB in every prim.

RyeDin, thank you.

But in this context (see my linked thread), it is the problem that the whole linked object moves as if I do click-drag it when I click on a button, a child prim. It is called "prim-drift".
If you see my linked thead of the linked thead, you'll find this is a deep-going bug of SL that Andrew Linden promised to fix by 1.5.

OK, Anyway, I set it on every prim. I've not experienced it yet. I'll report it here when it happens again. Thank you.

Ahh, sorry I misread the question. Yep, every prim (to really kill that dead horse)

Actually, to be more correct, you only need to set it in any prim that has a script containing a touch_start() event handler.

With no touch_start() handler, click-dragging will not happen.