When I use the keyboard to move the control points of the lines, there is a delay of about 1 second before the updated on the screen. and in version13, such results were updated instantly. This problem is related to the size of the font project; the larger the project size, the longer the delay.
Does this problem have anything to do with the new version’s enhanced antialiased rendering of lines? I actually prefer the version 13 rendering scheme, visible jaggedness can be visualized on the screen to tips a line is not perpendicular.
Also, please reinstate the hint icon about when the lines are crossed or tangent , without these tips it is not possible to accurately determine whether line intersections have been avoided.
When cutting between two nodes with the knife tool, V15 will not perform the cut operation, but simply add nodes to the line edges.
It does work, but you need to ensure the start and end of the cut line actually include the outline. If you want to cut through an existing point, then make sure you enable Snap to Points from the View menu. Maybe it should always be “on” with the Cut Contours feature.
FWIW the way we draw the outline is as fast as it can be.
Selecting a point and pressing Ctrl+Arrow key 5 or 6 times in a row,
The software (v15) is frozen and can’t feedback the operation process.
And I found that the screen update speed is related to the size of the project file, The difference in speed between the two software is double.
Check “Snap to point” to solve the problem, it is off by default.
The orthogonal auxiliary line that tips snaped target is too thick and black, look not very nice, should change the color and thickness.
The feedback after cutting is also slow.
5.1 Horizontal and vertical control lines are thicker and fainter than diagonal and curved control lines, and this doesn’t look natural. Vertical and horizontal lines should naturally coincide with pixel and be the thinnest.
5.2 The control lines look thicker and chunkier than the glyph outline line, which is not only a visual effect problem, but also functionally masks problems with the glyph lines, such as the lines are slightly non-vertical or non-horizontal.
5.3 Together with the symptoms of problem 2, it is suggested that user should be allowed to turn off anti-aliasing and revert to the real-time feedback speed of older versions until rendering appearance and performance is thoroughly refined.
Yes, this is clearly an issue. We will look into this, but it is rather complex as we continue to add more features to the software, and that tends to make it slower.
Issue 5.2 still has a big impact on FHD displays, maybe the screen resolution can be detected to determine whether to turn on the anti-aliasing switch, so Everybody’s satisfied.
Or add a new tip color line for slightly non-orthogonal state?
