llAllowInventoryDrop

With llAllowInventoryDrop turned on....

and with someone CTRL-dragging an item into a prim...

is there anyway you can capture who just did that?

I'm pretty sure you can't; just checking.

Chaz

There really isn't, to my knowledge and to that of the lslwiki.net wiki, which is unfortunate.

If add is true, all users, even those who do not have modify permissions, can drop inventory items onto the object. If add is false the system forbids all users except those with modify permissions from dropping items onto the object.

Ownership of the dropped inventory item changes to the owner of the prim, and next owner permissions are applied to the transfered inventory item.

The changed event handler is called with the CHANGED_ALLOWED_DROP flag when an item is dropped onto the object by a user that does not have modify permission. CHANGED_INVENTORY is passed to changed if someone with modify permission dropped the item.

The exception are scripts, attempting to drop a script onto an object which allows inventory drops will cause the object to shout "Not permitted to edit this!".
Scripts cannot be dropped by an agent onto a prim regardless of llAllowInventoryDrop state. (If a user without modify permissions tries to drop a script into a prim that allows inventory drop then the prim will shout "Not permitted to edit this!"
To upload a picture or a texture keep [ctrl] pressed and drag into / onto the prim

Note: If you declare llAllowInventoryDrop in the root prim of a linkset and then drop a texture onto a child, it will go into the child's inventory, NOT the parents. This is odd, as every other object will go to the parent's inventory.

default{
state_entry(){
llAllowInventoryDrop(TRUE);}
changed(integer mask){
if(mask & (CHANGED_ALLOWED_DROP | CHANGED_INVENTORY))
llWhisper(0, "My inventory has changed";
}}

Bwuh?

It's possible, as Olij explained.

No, it's not. I bwuh'd because he missed the point of the OP's question, which was 'Is it possible to know WHO dropped in the item,' to which the answer is 'No.'

It was a joke.

Right?

Would've been easier to tell but these forums are weeeeeeeeeeeeeird.

But hey, maybe you could require someone to touch before dropping or something. Not full proof, but starting from there and getting increasingly less user-friendly you could make it so

(EDIT: As "Day" Said)... you COULD do something whereby the "box" must be "touched" or in some way "told" to accept inventory. This might be through the use of a touch. Touch the box, and it checks your Group tag, or something.

Then it sets to allow inventory drop, and on inventory drop, it changes back to disallow status.. thereby "closing" the window. You could have it also say, set a timer, after which point it might close the "able to drop" window.

This would give you a change to record the name of the person who enabled the drop, and then the name or key of the item they (or someone within the X second window) dropped. If you keep your communications private (using llDialog or llInstantMessage) between Box and dropper, then the odds of someone standing there, KNOWING that the window is open, are slim.

Likewise, you could use a sensor.. and do a sweep for the "closest avatar when the drop was made".. imperfect I know, but depending on your application, perhaps you can make it work. (again perhaps a 1m scan area, and the avatar MUST "stand on the platform" in order to drop items.. without an avatar standing there, drop inventory is disabled.

Maybe make a little booth with a pad that says "stand here"... then when an avatar stands there, the Drop Box turns green. While it's green, all drops will be attributed to the peson on the pad.

Anyways, just some ideas for "working around" the problem.

I did something where an AV is forced to sit on the object to enable allowing inv drop.

That way you can detect the seated av. Still not secure as another av hanging about can do a drop at the same time. However depending on what it is, you should be able to only accept /process items created by etc the seated av.