Skip to content

Document usage limitations in AtlasTexture #107367

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Calinou
Copy link
Member

@Calinou Calinou commented Jun 10, 2025

@Calinou Calinou requested a review from a team as a code owner June 10, 2025 15:58
@Calinou Calinou added enhancement documentation cherrypick:4.4 Considered for cherry-picking into a future 4.4.x release labels Jun 10, 2025
@Calinou Calinou added this to the 4.5 milestone Jun 10, 2025
Copy link
Member

@Mickeon Mickeon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I... am not sure how true this is. It's a very vague statement, I feel. GPUParticle2D does support AtlasTexture (to an extent), and I know what you mean, but cases like these are anything but "basic contexts".
Big cardinal sin to say "basic", too.

This information is (annoyingly for maintainability) better put into each description where it matters.
Alternatively, if the properties that do support AtlasTexture are in the minority, their descriptions should specify that "AtlasTexture is supported"

@arkology
Copy link
Contributor

But NinePatchRect has AtlasTexture support.

@Calinou Calinou force-pushed the doc-atlastexture-no-3d branch from 3c3a882 to c906132 Compare June 11, 2025 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherrypick:4.4 Considered for cherry-picking into a future 4.4.x release documentation enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants