new changed event!

I was first thinking the whole change event should be modified, but then I realized it was really just one case that was so different from the rest.

There should be a new event handler:

changed_inventory(string name, integer type, key sender, integer received)

This would be triggered whenever the inventory changes from CHANGED_INVENTORY or CHANGED_ALLOWED_DROP.

If received is TRUE then the object gained an item. The rest of the parameters are then the name of the new item, its inventory type, and the ID of who or what gave it or dropped it.

If received is FALSE then an object left the inventory - something was deleted or a no-copy item was sent somewhere. In this case the first two are the same, but the last is the ID of where the item went. If it was a player that deleted or removed it, then it is that players ID, if a script on the object deleted it then it is NULL_KEY.

The second set isn't as critical to me as the first, in other words I would be happy if this only was triggered when new items were added to the inventory.

-----------------

P.S. I still want llGetInventoryPermissions(string name) really, really, really badly.

That'd be cool, but wouldnt work for situations that involve dropping a directory (folder) on an object (unless your willing to have *THAT* many events queueing).

[HIJACK]
Me personally, would like to see something like:

changed2(key changer, integer change)

Determining the value of the change is simple(IMO, unless it involves inventory, then you need to use a lovely list ), if you were previously monitoring what was changed. Getting the person or thing that changed the object, with the current system, is completely and utterly impossible.
[/HIJACK]

==Chris

Hey now, I started this thread so that I wouldn't hijack yours!

as for folders ... um ... there could be a new 'folder' type that just meant a whole lota crap was dropped on it (thats all a folder does) and you should act accordingly. Or even better - let objects have folders in them.