Skip to content
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

\pgfpointtransformed is mentioned, but not documented #844

Closed
projekter opened this issue Apr 10, 2020 · 2 comments · Fixed by #961
Closed

\pgfpointtransformed is mentioned, but not documented #844

projekter opened this issue Apr 10, 2020 · 2 comments · Fixed by #961

Comments

@projekter
Copy link
Contributor

Version: 3.1.5b

On page 1164, the documentation to \pgfpointtransformednonlinear reads:

Works like \pgfpointtransformed, but also applies the current nonlinear transformation...

However, \pgfpointtransformed is not documented at all - but it really should be, I'd say it is rather a rather important function.

For developers, it would also be nice to know what the recommended way for generic code (i.e. without knowing what the user specifies as a transformation) is: Always call the (more general?) nonlinear point transformation, or, as \pgfpathmoveto or \pgfpathlineto, always only call the linear one and execute special macros afterwards that deal with the nonlinear case (which probably then require some patching of \pgftransformnonlinear in order to install these commands.

@hmenke
Copy link
Member

hmenke commented Apr 10, 2020

Ultimately only @tantau can tell, but it looks to me like \pgfpointtransformed is deprecated and you should use \pgftransformrotate, \pgftransformshift, etc. instead. I'd argue the same applies to \pgfpointtransformednonlinear and you should use \pgftransformnonlinear instead.

@projekter
Copy link
Contributor Author

Those macros fulfill a completely different purpose - \pgftransformrotate and the like install the given transformation, so that all future points are transformed by this specification. \pgfpointtransformed is the way how this is actually achieved internally - it applies all transformations that are currently known to the given point and returns what comes out. All path construction macros call \pgfpointtransformed, so I can hardly believe it is deprecated.

@hmenke hmenke added this to the 3.1.6 milestone Apr 14, 2020
@hmenke hmenke modified the milestones: 3.1.6, 3.1.7 Sep 28, 2020
muzimuzhi added a commit to muzimuzhi/pgf that referenced this issue Dec 17, 2020
muzimuzhi added a commit to muzimuzhi/pgf that referenced this issue Dec 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants