secondlife / secondlife/viewer

Make permissions preset for created Materials easier to understand

Open
#3,070 6 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

bug stale team:viewer UX design
Dominant language
C++
Stars
299
Forks
146
Avg merge
1d 9h
Merged PRs (30d)
88

Description

This Default Creation Permission are working correctly, but the UI is confusing. (I too was confused while investigating this until Whirly discovered the tooltip.)

The Default Creation Permission to change for uploaded Materials is the Uploads category.

The Materials permission in that floater applies only to Materials that are created new in the Inventory. The tooltip for Materials says that that's what it's for but the UI should be more clear, ideally visible without reading a tooltip.

Also consider changing the icon for Uploads to something other than the Texture icon. Something that suggests "uploading".

Maybe the Uploading should be changed to Uploading (with all the things that can be uploaded in parenthesis)

Image


Original report:

  1. Under Preferences, Advanced, Default Creation Permissions (DCP). Set Materials to Copy.

  2. Upload Material, select a .glb file and bulk selection for textures.

  3. Materials upload as Modify, Copy, Transfer NOT the DCP setting of Copy.

Note: During the upload above Texture DCP were set to Modify, Copy, Transfer. This overrode the Material DCP setting.

In the scenario above the correct outcome would be materials to be set as Copy, not Modify, Copy Transfer as it's using the material upload function not the texture upload function from a hierarchy standpoint. However, the Texture DCP is overriding what is set for Material DCP.

Note this is present in Firestorm too as well as the LL Viewer.

https://secondlife.canny.io/admin/board/bug-reports/p/materials-are-uploading-with-incorrect-permissions

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.