
|
If you were logged in you would be able to see more operations.
|
|
|
| Linden Lab Issue ID: |
SL-44934
|
| Patch attached: |
Patch attached
|
|
When abuse-reporting an object, the abuse report tool takes the object information and owner information, however it requires the object-owner's name to be filled in a second time, presenting an additional step to completion.
The abuser name should be prefilled in the abuse-report floater as the object owner is acquired. This is neither a very large nor a very urgent item.
|
|
Description
|
When abuse-reporting an object, the abuse report tool takes the object information and owner information, however it requires the object-owner's name to be filled in a second time, presenting an additional step to completion.
The abuser name should be prefilled in the abuse-report floater as the object owner is acquired. This is neither a very large nor a very urgent item. |
Show » |
|
Behavior details:
- When an OBJECT is selected with the object selector tool, the owner's name and UUID are filled in for the abuser information. (This also applies when using the pie menu on an object and selecting More.. > More... > Report Abuse...)
- When an AVATAR is selected with the object selector tool, the avatar's name and UUID are filled in for the abuser information.
- (This doesn't change the behavior of the "Name:" and "Owner:" fields that are located a little bit under the selector button. Only the "Abuser name:" field and the hidden mAbuserID variable are affected.)
In the course of implementation, I added an additional argument to LLFloaterReporter::setPickedObjectProperties(). This allows LLSelectMgr::processObjectPropertiesFamily() to pass along the UUID of the object's owner. Grep doesn't show the set...Properties() function being used anywhere besides that one spot in the viewer code, but someone should double-check that it isn't used elsewhere (and maybe the server code, too -- but I really doubt it's in there).