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

(Qt6) Depreciations fixes #1614

Open
wants to merge 1 commit into
base: qmltoqt6
Choose a base branch
from
Open

(Qt6) Depreciations fixes #1614

wants to merge 1 commit into from

Conversation

Ledjlale
Copy link

  • Fixes some binding loops (QML).
  • Fixes some deprecated callback uses (QML).
  • Fixes missing namespace (QML).
  • Fixes warnings on potential null values (QML).

@Ledjlale Ledjlale marked this pull request as draft September 12, 2024 10:16
@Ledjlale Ledjlale changed the title Qt6 Depreciations fixes (Qt6) Depreciations fixes Sep 12, 2024
@coveralls
Copy link

coveralls commented Sep 12, 2024 •
edited
Loading

Coverage Status

coverage: 31.426%. remained the same
when pulling 63f1ce2 on Ledjlale:fix/qt6_depreciations
into 606b850 on mcallegari:qmltoqt6.

@Ledjlale Ledjlale force-pushed the fix/qt6_depreciations branch from bb16e6e to db62017 Compare September 18, 2024 11:47
@Ledjlale
- Fixes some binding loops (QML).
63f1ce2 
- Fixes some deprecated callback uses (QML).
- Fixes missing namespace (QML).
- Fixes warnings on potential null values (QML).
@Ledjlale Ledjlale force-pushed the fix/qt6_depreciations branch from db62017 to 63f1ce2 Compare September 18, 2024 11:47
@Ledjlale Ledjlale marked this pull request as ready for review September 18, 2024 11:48
@mcallegari
Copy link
Owner

Hey thanks for this but can we please split it?
I'd start with "Fixes some deprecated callback uses" which looks like the biggest thing
Thank you

@Ledjlale
Copy link
Author

Hi, I'm sorry but since the new policy of Github about their two-factor authentication that become a mandatory, I will not continue to participate any longer till I get a new solution (and time to switch).
Regards

@yestalgia
Copy link
Contributor

Hi, I'm sorry but since the new policy of Github about their two-factor authentication that become a mandatory, I will not continue to participate any longer till I get a new solution (and time to switch). Regards

If there's anything we can do to help please let us know

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@Ledjlale @coveralls @mcallegari @yestalgia