Skip to content

Conversation

skef
Copy link
Contributor

@skef skef commented Apr 3, 2022

Closes #4976

This is specific enough that I don't think it needs automated tests. I did basic checks on each of the flags.

return( NULL );
// Flip fvt_alllayers back
if ( flags&fvt_alllayers )
flags |= fvt_alllayers;
Copy link
Contributor

Choose a reason for hiding this comment

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

Why is this needed? Isn't this a no-op?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The intention was to have fvt_alllayers in the python flags be opposite to that in the flags passed down (as its supposed to be on by default). I'll take a look later.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's going to be Wed evening at the earliest before I could do something about this properly, but I believe the line should read flags &= ~fvt_alllayers; . I just goofed it, apparently. If that makes sense to you and you want to integrate early, go ahead.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

OK, had time to actually look at and revise this. I just had the two bit-flipping lines in the wrong positions.

@skef skef merged commit 881d85c into fontforge:master Apr 29, 2022
Omnikron13 pushed a commit to Omnikron13/fontforge that referenced this pull request May 31, 2022
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

Successfully merging this pull request may close these issues.

Python font.transform(psMat.scale(FACTOR)) does not give the same result as Scale Uniformly in the GUI.
2 participants