Closed conkererer closed 7 years ago
The \fade(n1,n2) error in MotionHandler is not actually getting thrown in the current master since it converts it into a transform
Still really confused whether \fade(n1,n2) is valid or not since the regex used in Tags.moon and elsewhere is "\fade?%((%d+,%d+)%)", so that might be an error
That was in there because while that tag is erroneous, I received multiple complaints that aegisub-motion wasn't working correctly from people who, unfamiliar with the inner horror of ASS or simply illiterate, had used \fade(100,100)
instead of \fad(100,100)
. I decided it was a better solution to steamroll this mistake than to ignore it or have it cause an error.
90% functional, only bug left is fixing the way it gets alpha values in the first block couldn't figure out how to get the Line functions to work properly in the MotionHandler, dunno if that's broken or something
Made some improvements to roto handling while I was at it, even though it seems I'm the only one that uses this feature
The pull request name is as appropriate as ever. Thanks for doing all the work.
I don't see any obvious problems, but I'm going to squash this down into only a few commits before merging it.
Still really confused whether \fade(n1,n2) is valid or not since the regex used in Tags.moon and elsewhere is "\fade?%((%d+,%d+)%)", so that might be an error
These changes are kinda tested, probably work fine, but would maybe make processing by other script harder since \fade tags are not used that often