CP_Font_Free is no longer in the API (cprocessing.h) but it is still in the wiki as a broken link.
CP_Font_Load's example still references CP_Font_Free.
Without CP_Font_Free, users noticed an inconsistency between CP_Font's and CP_Image's API. CP_Image has a Load/Free pair while CP_Font does not, which causes users to be confused about CProcessing's philosophy behind resource management. Users who are monitoring their RAM usage also prefer to have a way to free their fonts (for example, using one set of fonts for state A and using another set of fonts for state B).
I suggest that we reintroduce CP_Font_Free to allow users to have full control over their application's memory management. When time permits, we will implement this and test in the Singapore branch first.
CP_Font_Free is no longer in the API (cprocessing.h) but it is still in the wiki as a broken link. CP_Font_Load's example still references CP_Font_Free.
Without CP_Font_Free, users noticed an inconsistency between CP_Font's and CP_Image's API. CP_Image has a Load/Free pair while CP_Font does not, which causes users to be confused about CProcessing's philosophy behind resource management. Users who are monitoring their RAM usage also prefer to have a way to free their fonts (for example, using one set of fonts for state A and using another set of fonts for state B).
I suggest that we reintroduce CP_Font_Free to allow users to have full control over their application's memory management. When time permits, we will implement this and test in the Singapore branch first.