This has been discussed a little bit, including in #1577 (specific comment) and @lorenzncode already experimented with this in #1525 . This might help with issues like #650 as well, but I am not sure.
In the case of #1577 I found that I would get a silent failure when I entered an invalid font name or path. Tying into OCCT's message mechanism reveals the error. With a messaging interface in CadQuery, users could enable more verbosity from the OCCT layer. This could take the form of what @lorenzncode has laid out in #1525 (link to changes).
This has been discussed a little bit, including in #1577 (specific comment) and @lorenzncode already experimented with this in #1525 . This might help with issues like #650 as well, but I am not sure.
In the case of #1577 I found that I would get a silent failure when I entered an invalid font name or path. Tying into OCCT's message mechanism reveals the error. With a messaging interface in CadQuery, users could enable more verbosity from the OCCT layer. This could take the form of what @lorenzncode has laid out in #1525 (link to changes).