-
Notifications
You must be signed in to change notification settings - Fork 216
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
\t argument parsing: missing comma #91
Comments
Why would you expect it to be shifted downwards? That’s \fad, not \pos. |
2 lines on the same layer; the second gets shifted to prevent overlap? I forget the name for it. |
O-oh, because there is no \pos. Yeah. (In libass this is called collision… er… well, just collisions.) Hm… I’ll have to actually test this in VSFilter before I believe it. inb4 I missed something obvious |
I went back and forth with skiddiks on this for a while, not believing that it worked in VSFilter, but he's quite insistent that it's fine. |
if(!fPosOverride && !fOrgOverride && !s->m_fAnimated)
r = m_sla.AllocRect(s, segment, entry, stse.layer, m_collisions); and |
Confirmed in guliverkli (VSFilter 2.37) code as well. |
But we already disable collision detection on \t. Oh! There we go. This is a parsing bug and a bug in the script. |
See #94. |
Fixed by cc9aaeb. |
Apparently in VSFilter, these 2 lines appear overlapped at the same position. In libass, the second one is shifted downwards (as I'd expect it to be). Hell if I know why VSFilter doesn't follow the usual behavior here.
The text was updated successfully, but these errors were encountered: