Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Provide Interface to OCCT Messages #1582

Open
jmwright opened this issue May 6, 2024 · 0 comments
Open

Provide Interface to OCCT Messages #1582

jmwright opened this issue May 6, 2024 · 0 comments
Labels
enhancement New feature or request OCC feature Requires coding at OCC implementation level

Comments

@jmwright
Copy link
Member

jmwright commented May 6, 2024

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).
@jmwright jmwright added enhancement New feature or request OCC feature Requires coding at OCC implementation level labels May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request OCC feature Requires coding at OCC implementation level
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jmwright