Skip to content

Conversation

@justvanrossum
Copy link
Member

@justvanrossum justvanrossum commented Jan 7, 2026

Fixed my bad assumption: it turns out Glyphs App replaces the entire .glyphspackage folder on "save", (with even all .glyph files having new modification times) and we don't receive change events for any files inside the .glyphspackage folder.

There's no easy way to make this more efficient than just reading everything back in. This is accomplished by removing the the specialized fileWatcherProcessChanges method in GlyphsPackageBackend, and let the superclass GlyphsBackend do the work.

…ckage: turns out Glyphs App replaces the *entire* .glyphspackage folder (with even all .glyph files having new mtimes) and we don't even receive change events for the files *inside* the .glyphspackage folder. So there's no easy way to make this more efficient than just reading everything back in
@justvanrossum justvanrossum merged commit 103b651 into main Jan 7, 2026
1 check passed
@justvanrossum justvanrossum deleted the fix-glyphspackage-for-glyphsapp branch January 7, 2026 09:57
@justvanrossum justvanrossum changed the title Fix watching changes in .glyphspackage folders Fix responding to external changes in .glyphspackage folders Jan 7, 2026
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.

2 participants