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.

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

Debugging qml for a plugin #911

Open
Ant0ine64 opened this issue Oct 3, 2023 · 1 comment
Open

Debugging qml for a plugin #911

Ant0ine64 opened this issue Oct 3, 2023 · 1 comment

Comments

@Ant0ine64
Copy link

Ant0ine64 commented Oct 3, 2023

Hi, I'm trying to create a plugin but it seems when I have some invalid qml, I'm not able to know what's wrong with it, I can't see anything in the logs. (By invalid I mean, adding some invalid statements made out of randoms letters)

The plugins adds a tool, when in getMetaData() I give either a wrong qml file path or a qml file with something wrong, nothing happens when I click on the tool icon in cura.

I think this is a code concerned but it does not give any error:
https://github.com/Ultimaker/Uranium/blob/main/UM/Qt/Bindings/ActiveToolProxy.py#L43
https://github.com/Ultimaker/Cura/blob/main/resources/qml/Toolbar.qml#L206

I would really appreciate if anyone could give me advice on how to debug some thing like this.

@dfries
Copy link

dfries commented Sep 2, 2024

When you run cura add --debug to the command line. Now,

ClearlyNotAvailableComponetName { }

Will print the following to stdout/stderr

share/cura/resources/qml/Actions.qml:13:5: ClearlyNotAvailableComponetName is not a type

Please close your request if this solves your issue.

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

No branches or pull requests

2 participants