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

Consider which attributes should be on a Q_PROPERTY #42

Open
ahayzen-kdab opened this issue Dec 9, 2021 · 2 comments
Open

Consider which attributes should be on a Q_PROPERTY #42

ahayzen-kdab opened this issue Dec 9, 2021 · 2 comments
Labels
🤔 discussion Feedback welcome ⬆️ feature New feature or request 🥳🎉 1.0 This issue is part of stabilization for 1.0 release
Milestone

Comments

@ahayzen-kdab
Copy link
Collaborator

ahayzen-kdab commented Dec 9, 2021

Have the ability to declare a #[property(getter = "...", setter = "...", notify = "...")]

For example we can't currently say that a property is readonly to C++/QML, but note that this would require the setter to still be accessible from Rust. Does this simply mean which Q_PROPERTY attributes as set?

@ahayzen-kdab ahayzen-kdab added the ⬆️ feature New feature or request label Dec 9, 2021
@ahayzen-kdab ahayzen-kdab changed the title Consider which attributes should be in the data struct Consider which attributes should be on a Q_PROPERTY Oct 3, 2022
@ahayzen-kdab ahayzen-kdab added this to the 0.5 milestone Oct 3, 2022
@ahayzen-kdab ahayzen-kdab added the 🤔 discussion Feedback welcome label Nov 2, 2022
@ahayzen-kdab ahayzen-kdab modified the milestones: 0.5, 0.6 Jan 10, 2023
@ahayzen-kdab
Copy link
Collaborator Author

This is being worked on in #451 by @CarlSchwan

@LeonMatthesKDAB LeonMatthesKDAB added the 🥳🎉 1.0 This issue is part of stabilization for 1.0 release label Jan 17, 2024
@LeonMatthesKDAB
Copy link
Collaborator

Now being worked on in #994 by @BenFordTytherington

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤔 discussion Feedback welcome ⬆️ feature New feature or request 🥳🎉 1.0 This issue is part of stabilization for 1.0 release
Projects
None yet
Development

No branches or pull requests

2 participants