This topic is also mentioned in incorrect number of fonts in collection shown
In reply to
Just to clarify, I completely understand your point and see how it makes total sense
Although I am not among the majority you’ve mentioned in your question and don’t feel it’s applicable to myself, you’ve mentioned a very interesting idea.
What does everyone here think about adding a context menu option (currently containing Activate/Deactivate, Package, Delete) to “remove old” or “remove obsolete” option, or “update”, which would remove the fonts from a collection which are currently not present in the app?
One of the concerns with making this process automatic is that a considerable part of FontBase users use network drives (NAS, GDrive, Dropbox etc) to store fonts, and in case of the connection breaking or something happening to the network even for a short duration the situation would be virtually indistinguishable from the fonts being deleted from a hard drive. As a result, when the connection is restored, the Folders in FontBase will update, but the Collections will have lost these fonts forever, potentially wasting many hours of sorting sometimes thousands of fonts. We used to receive a great deal of reports about this happening in the past, hence the introduction of the “collection memory” feature if you will. Basically separating the removal of fonts from a collection and the removal of fonts from FontBase font tracking. As @PB-CCC mentioned in the initial post, the issue arose when removing fonts from the hard drive, not removing fonts from a collection by dragging and dropping them in the Bin are on the right side of the app window.
Thank you again,