Blender - field name collision, confusing #102438
Labels
No Label
Meta
Good First Issue
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Eevee & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds, Tests & Devices
Module
Python API
Module
Rendering & Cycles
Module
Sculpt, Paint & Texture
Module
User Interface
Module
VFX & Video
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-manual#102438
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits
Blender Version
Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-10-21 18:48, hash:
blender/blender@04eab0fd01Short description of error
[Please fill out a short description of the error here]
On this page:
https://docs.blender.org/manual/en/dev/modeling/geometry_nodes/texture/brick.html
reference brick texture, and the field name 'Frequency' is duplicated from two completely different contexts. Very confusing for reader as well as users to distinguish which is which.
Please change the field text in code and in documentation.
Added subscriber: @hoanguk
Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Added subscribers: @HooglyBoogly, @PratikPB2123
Changed status from 'Needs Developer To Reproduce' to: 'Archived'
I don't think this sort of tweak should be handled as a bug. It's definitely not ideal, but it's using the same order as the UI, so it makes sense on some level. Better to get involved with the documentation process to help improve things there.