blackfoundry / trufont Goto Github PK

Double-clicking on a contour selects all its points.

But no undo-action is associated with the process, so that performing undo undoes the last action, but not the select-all that we just did.

One should add this undo/redo action pair, so as to be consistent with the rubber-band selection which is undoable.

Unit tests on internals and functional tests interface (?)
Validation before producing binaries on 3 systems (MacOS, Windows, Linux)

When a pop over is opened in the glyph window, clicking on UI buttons has no effect, the mouse events are 'locked' somewhere. Only a double-click release the mouse and makes further clicking in UI possible

Nice Python scripting window editor.

Per harfbuzz/harfbuzz#1554 (comment)

the conversion does not seem to work.

no undo/redo linked to glyphs other than the first of a string in a tab.
May be because the undo redo manager is linked to the tab instead of the glyph?

Too many not implemented features.
To be listed and completed.

With the selection tool (the first tool), move a corner point, then release the mouse, and without moving the mouse, click again and drag the corner point (sharp point, square blue marker) : oops! the points moves way too fast.

In the UFO v4 discussions, https://www.sqlite.org/appfileformat.html came up as a good suggestion, and I think makes a strong argument. I also now see https://www.sqlite.org/affcase1.html which presents a case study; the 'versioning' section was very interesting to me, as was the link to https://www.sqlite.org/undoredo.html

With the current UndoManager, I expect that version support plus the overall "ZIP like" properties of sqlite could be very relevant to the project.

While .tfont files are OK for now, this may be a superior alternative.

Write docstrings for all the exiting

The patch of 'Yves PaintDC' branch is actually fixing the wx bug issue for the most. And @adrientetar told me he knows how to fix the layer's color box issue too.

Please merge these two branches @YvesDup

I would like to suggest setting up a few milestones, and a set of priority tags.

• P0, for things that should be done before anything else (eg crashing bugs preventing real work from happening)
• P1, for things that should have progress each week
• P2, for things that should have progress each month
• P3, for things that are interesting candidates for scheduling in the future ("Someday, Maybe")

Milestones allow a "list" or "stack rank" ordering of issues, a percentage based view of completion on the milestones page, and a target date for all issues to be resolved.

Eg #11 seems more like a Milestone than a single issue :)

• Refactor penTool functions that are too long and do too many things on mouse down.

• Add more documentation to make code more legible.

• Refactor penTool functions that are too long and do too many things on mouse down.

• Add more documentation to make code more legible.