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

[bug]Text position matrix operation is incorrect #1984

Open
Danjuanlab opened this issue Feb 10, 2020 · 3 comments
Open

[bug]Text position matrix operation is incorrect #1984

Danjuanlab opened this issue Feb 10, 2020 · 3 comments

Comments

@Danjuanlab
Copy link

I have a project that is useful for dynamic layout. I tried to use expressions in AE to accomplish this purpose, but when exporting animation, the position of the text in the web page is different from that in AE. I found that the data in the position matrix of the text on the front end of the webpage is different from that in AE.
OS:win10 64bit
AE2019

1
2

sample.zip

@Danjuanlab
Copy link
Author

@bodymovin I inadvertently debugged and found that this error seemed to originate from the order in which the expressions were evaluated. Place the graphics layer above the text layer, and the export result is correct. So my guess is that when generating the json file, the text position is calculated first. At this time, the text expression is calculated based on the original data of the graphic.

@bodymovin
Copy link
Collaborator

This is also related to sourceRectAtTime, unfortunately, when using this method, the order of expression evaluation is not respected because the element needs to be rendered to calculate its size.

@Danjuanlab
Copy link
Author

Danjuanlab commented Mar 1, 2020

This is also related to sourceRectAtTime, unfortunately, when using this method, the order of expression evaluation is not respected because the element needs to be rendered to calculate its size.

Thanks for your information, I will think again if there is a way to achieve dynamic size change without applying this sourceRectAtTime. However, for the design of dynamic width interactive UI controls, this function seems to be inevitable. I hope that there are plans to optimize it in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants