Previous owner with llAllowInventoryDrop?

Sorry to bug ya'll with this but I just can not find the answer - probably looking for the wrong thing.

I'm trying to figure out how to have a script determine WHO put a texture into a prim when I use llAllowInventoryDrop but for the life of me I cant seem to figure it out! Any help would be appreciated thanks!

You can't. Sorry. This is THE most common question regarding the llAllowInventoryDrop() mechanism, so if you do a search on that function name in this forum you'll probably find lots of useful information. I'll give you the most common answer though: usually people require a resident to touch the prim before dropping the item in (that's when llAllowInventoryDrop() is turned on), and they only leave llAllowInventoryDrop() on for a short period to try to ensure the person who touched it is the person who drops the item. You can also provide a feature where the person who did the touch can somehow undo or overwrite the change just in case someone else sneaked in at the wrong moment.

Oh you're brilliant! I did search for llAllowInventoryDrop but must have misspelled it something because I came up with nothing - but that is a brilliant answer to my dilemma thank you!!!!

think "You just added _______________. [Give Back] [Save] [Delete]"

You can also do some neat things with "checking permissions" of the received item. If it's no transfer, the script can hide the "Give back" button. if it's copyable the "give back button" can say "Examine".. once pressed, it could give a copy of the item to the clicker.. and then go into a loop where it checks to see that the inventory is still there, and pops the dialog "so what would you like to do?"

You can also use a sensor.. to scan for that person's presence. You can then act differently based on certain things.. Like if it's been a while you can pop up a dialog using the same menu channel, that says "Sorry to be a pest about this, but you haven't responded."... you could also actually STORE the keys of people in a list, and scan for those people.. so if they left, you could pop a dialog when they returned (if they crashed or something). after half an hour, you can just store the item..

Then it's just a matter of either storing the information, or dumping it out. You can do things like "send an email"..

received "Staff Application"
from "Janet Gooding"
date Thu May 15, 2008 13:54 GMT
status Saved

received "Staff Application"
from "Michael Gooding"
date Thu May 15, 2008 14:54 GMT
status No response

Is there a JIRA on this? I guess this is a function that'd be pretty handy...

I tried to find a workaround for this, so I tried something like this:

key inv_key = llGetInventoryKey("my_inventory_item";
key owner_key = llGetOwnerKey(inv_key);

interestingly, inv_key and owner_key produce the same result...?