Relative Paths #43546
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#43546
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?
The use of relative paths in Blender (e.g.
//../textures/img.png
) is quite important and enabled by default, however it is not documented anywhere what exactly a relative path is, compared to the usual absolute paths (e.g./home/user/projects/test/textures/img.png
). It is not a common term for windows users and thus can cause some confusion.A page should be added to the Data System chapter which explains them properly, where they are used and what problems they might cause (e.g. moving a blend file using the OS's file browser will most likely break all texture and library paths in the blend file).
Then wherever relative paths are mentioned prominently, a link should be added pointing to this page.
Changed status to: 'Open'
Added subscriber: @GregZaal
Shall we assume readers know, or can find out, what a relative path is. It seems we shouldn't have to explain path hierarchy and define the terms.
Perhaps we can just briefly explain it - no need to go into too much detail. Might be a good idea to link to somewhere (e.g. wikipedia) that explains it more thoroughly.
This issue was referenced by 271
Changed status from 'Open' to: 'Resolved'
Closed by commit rBM271.
Very nice!