Fragment `zbrush.commands.resolve_path`¶

Code fragment for zbrush.commands.resolve_path.

zbrush.commands.resolve_path

Makes the given relative path absolute in relation to the directory of the executing Python module.

Code¶

"""Code fragment for zbrush.commands.resolve_path.
"""
__author__ = "Ferdinand Hoppe"
__date__ = "16/10/2025"
__copyright__ = "Maxon Computer"

from zbrush import commands as zbc

import os
import sys

# Let's assume we have this directory structure:
#
#   D:
#   └── scripts
#       ├── my_script.py
#       └── my_data.txt
#
# And the module we are currently running is #my_script.py. Then we can infer the absolute
# path to 'my_data.txt' as follows:
abs_data_path: str = zbc.resolve_path("my_data.txt") # > "D:\\scripts\\my_data.txt"

# As many for these legacy Zscript functions, it is a bit questionable to use a function
# for something this simple when using Python. We can achieve the same just by using #os
# and #__file__
abs_data_path_os: str = os.path.join(os.path.dirname(__file__), "my_data.txt")

# It is also really important to understand that the working directory of this Python script
# is NOT the directory of the script itself as one might be used to from a CPython instance, 
# but the directory of the running Zbrush instance.
print(f"{os.getcwd() = }")   # Will print the installation location of ZBrush.

# This will NOT try to open a file "my_data.txt" next to the file of this module but a file
# of that name in the ZBrush installation directory (because relative paths are releative to
# the working directory).
with open("my_data.txt", "r") as f:
    data = f.read()
    print(f"{data = }")

# Changing the current working directory is not advisable, as you do not just do this for
# your script, but for all scripts the user will ever run. And some scripts might implicitly
# rely on the current working directory being the ZBrush installation directory. So, we
# should use absolute paths instead.
data_file: str = os.path.join(os.path.dirname(__file__), "my_data.txt")
with open(data_file, "r") as f:
    data = f.read()
    print(f"{data = }")

Category	Option	Description
Query		The search does not support special search operators. Terms are joined by default with OR unless the AND join mode is enabled. Queries can contain search literals denoted by double quotes. E.g., `foo bar` would search for documents that contain `foo` and/or `bar` (depending on the selected join option). But `"foo bar"` would search for the exact phrase "foo bar". The search is case-insensitive. Note that search literals will always implicitly enable strict search mode, even when the user has selected fuzzy mode.
	/	Toggles the visibility of the facet selection panel.
	/	Toggles the visibility of this help panel.
	OR / AND	Toggles between joining search terms with a logical OR or AND. In OR mode, the search will return results that match any of the search terms, while in AND mode, it will only return results that match all of the search terms.
	/	Toggles between fuzzy and strict mode when searching. In fuzzy mode, the search is more lenient and may return more results, while in strict mode, the search is more exacting. Switching modes may affect the relevance of the results.
	/	Toggles between detailed and compact result views. The detailed view shows more information per search hit.
	/	Toggles sorting the search results by relevance only or by a combination of classification and relevance. When sorting by classification and relevance, results are grouped by their type (e.g., pages, classes, methods) and then sorted by relevance within each group.
Facets		Facets restrict the search to specific content types. You must have at least one facet enabled per facet group to see any results. Domain is the largest facet group, enabling or disabling whole groups of content types. Entities are the next level down, allowing you to search within specific types of content such as generic pages or a function definition. Contexts are the most granular level, allowing you to search within specific contexts of the selected entity such as a code block ot the name of an entity.
Domain	API	Enable matches within API documentation pages.
	Manuals	Enable matches within general documentation pages.
	Examples	Enable matches within example pages.
Entity	Page	Enable matches within a page body that are not one of the following entities.
	Classes	Enable matches within class definitions.
	Methods	Enable matches within class method definitions.
	Functions	Enable matches within module function definitions.
	Attributes	Enable matches within class or module attribute definitions.
Context	Paragraphs	Enable matches within normal text paragraphs of a page.
	Headings	Enable matches within the headings of a page.
	Code	Enable matches within code blocks of a page (e.g., in the Examples domain or code blocks embed elsewhere).
	Names	Enable matches within the names of API entities. This searches the plain names (`func`), not the qualified names (`foo.bar.func`).
	Signatures	Enable matches within the signatures of API entities. The signature is what is shown on top of the entity description, e.g., `foo.bar.func(a: int, b: str = "Hello") -> bool`. When you want to search for fully qualified names, you should enable this option and disable the "Names" option.
	Metadata	Enable matches within the metadata of entities.

Fragment zbrush.commands.resolve_path¶

Code¶

Search

Fragment `zbrush.commands.resolve_path`¶