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

Bugfix/qml warnings #3388

Merged
merged 6 commits into from
Jun 16, 2021
Merged

Bugfix/qml warnings #3388

merged 6 commits into from
Jun 16, 2021

Conversation

camilasan
Copy link
Member

Partially fix #3070.
Most of these warnings were related to the User Status feature.
There are more PR's coming to fix some of these warning in other parts of the QML code.

@allexzander allexzander self-requested a review June 7, 2021 13:15
width: 128
text: name
elide: Text.ElideRight
color: "black"
font.pixelSize: Style.topLinePixelSize
font.bold: true
}
Row {
RowLayout {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we really need a RowLayout inside another one ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried to go back to Row but I found it harder to keep Linux and Windows the same when comes to aligning the emoji with the message.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

my question was more about getting rid of the parent element and just using the parent RowLayout item
maybe it is just too hard to fix alignment issues in that case but I am wondering if that is possible (and that would reduce complexity)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check my last commit. let me know if that is better or worst...

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

they are looking fine for me

@camilasan camilasan force-pushed the bugfix/qml-warnings branch 3 times, most recently from 2508dd4 to 0c23fd3 Compare June 8, 2021 18:08
@camilasan camilasan force-pushed the bugfix/qml-warnings branch from 0c23fd3 to c9ecdc0 Compare June 14, 2021 19:54
@camilasan camilasan force-pushed the bugfix/qml-warnings branch from c9ecdc0 to d7336d2 Compare June 15, 2021 11:15
@camilasan
Copy link
Member Author

/rebase

@github-actions github-actions bot force-pushed the bugfix/qml-warnings branch from d7336d2 to 6bb2ac9 Compare June 15, 2021 16:28
@mgallien
Copy link
Collaborator

/rebase

Camila added 6 commits June 16, 2021 07:55
Signed-off-by: Camila <hello@camila.codes>
…out.

Signed-off-by: Camila <hello@camila.codes>
…de Row.

Signed-off-by: Camila <hello@camila.codes>
… in theme.h.

Signed-off-by: Camila <hello@camila.codes>
Signed-off-by: Camila <hello@camila.codes>
Signed-off-by: Camila <hello@camila.codes>
@github-actions github-actions bot force-pushed the bugfix/qml-warnings branch from 6bb2ac9 to 7ddc4ca Compare June 16, 2021 07:55
@nextcloud-desktop-bot
Copy link

AppImage file: Nextcloud-PR-3388-7ddc4ca170e3b5b363ba60b16a31e4c49981d2a1-x86_64.AppImage

To test this change/fix you can simply download above AppImage file and test it.

Please make sure to quit your existing Nextcloud app and backup your data.

@camilasan camilasan merged commit 9ea8dd9 into master Jun 16, 2021
@camilasan camilasan deleted the bugfix/qml-warnings branch June 16, 2021 08:40
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

Successfully merging this pull request may close these issues.

Fix QML warnings
4 participants