Replies: 2 comments
-
|
The changed callback are documented there:
I think bug in the documentation can be reported as bug reports.
There is a link to the Rust and C++ documentation. Should there be more? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your answer! For the first one, it's great that they are documented, I thought there were no docs at all, which is why I wanted to open an issue. I personally think it still makes sense to mention the 'changed' in the "callbacks" section of the reference; since they are more related to callbacks than references. (this would be better if I google results for "slint property changed callback" were actually relevant, but for now I have to search by clicking through the docs) For image, I find it's unclear from the description that an image can be created programmatically, instead of just loading from a file. Even the text around the link you mention only says that one can access image properties programmatically, not create an image from scratch and assign it. It is visible when one follows the link, so not a big problem. In resume, turns out I was wrong and everything is documented somewhere, but if I may propose some clarity improvements, here they are above. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Didn't create an issue since I couldn't find a suitable category in the template, but I think it's an issue in the docs.
I was looking for the
changed width => {}syntax, and couldn't find it in the docs, until I stumbled upon the blogpost from 19-th august. I think this information should be in https://docs.slint.dev/latest/docs/slint/reference/common/ , as it is a common callback type to all components.On an unrelated note, I think https://docs.slint.dev/latest/docs/slint/reference/primitive-types/#image should mention that a slint::Image could be created in rust/c++ as well.
Beta Was this translation helpful? Give feedback.
All reactions