Page MenuHome
Create Task
Maniphest T73025

Data names beginning with "." are not recognized in lists
Closed, ArchivedPublicKNOWN ISSUE
Actions

Description

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31

Blender Version
Broken: 2.79 and latest 2.81 (sub 16), branch: master, commit date: 2019-12-04 11:32, hash: rBf1aa4d18d49d
Worked: Never?

Short description of error
Data names beginning with "." (dot) dont show up in lists.
For example: a material with the name ".Name".

What I have seen so far is that many if not all data lists are affected. But not the relations list for object parenting and object names.

Exact steps for others to reproduce the error

Event Timeline

Karja Krähwald (karja) created this task.Jan 10 2020, 4:48 PM
Dalai Felinto (dfelinto) changed the task status from Needs Triage to Confirmed.Jan 10 2020, 5:09 PM
Dalai Felinto (dfelinto) triaged this task as Low priority.
Dalai Felinto (dfelinto) updated the task description. (Show Details)
Dalai Felinto (dfelinto) changed the subtype of this task from "Report" to "Known Issue".
Dalai Felinto (dfelinto) added a project: User Interface.
Dalai Felinto (dfelinto) added a subscriber: Dalai Felinto (dfelinto).

This has been going on forever. Documenting as known issue, but setting priority as low since clearly it hasn't been a pressing matter for all this time.

Dalai Felinto (dfelinto) added a comment.Jan 10 2020, 5:11 PM

(and thanks for the report)

Julian Eisel (Severin) closed this task as Archived.EditedJan 10 2020, 5:12 PM
Julian Eisel (Severin) claimed this task.
Julian Eisel (Severin) added a subscriber: Julian Eisel (Severin).

This is actually a feature, not a bug :)
Data-blocks use the Unix convention of considering items starting with a "." as hidden. You can disable this under Preferences → Save & Load → Hide Dot Files/Data-blocks - which for some reason is placed in the "File Browser" panel...
While this is not respected everywhere, it is in cases like this.

So thanks for the report, but fortunately no bug here :)