On Sunday 22 January 2017, you wrote: > I think I filed one there at some point, but am no longer certain. With my > job change the last six months have been a bit quieter. The things that I > recall reporting include (and I never know if they are QML bugs or > Kirigami bugs)
I would prefer having some qml bugs reported there that I would mark as upstream, than not having reports at all, makes easier to keep track of issues, ours or otherwise > - scrolling problems at the bottom of the dive list when things suddenly > go blank or wildly jump around > - crazy layout issues where in grid layouts things get cut off at the > right edge - we ended up working around all of them by no longer > allowing the grid to resize > - no cut and paste to text fields > - positioning issues with the keyboard (so if I tap on a text field and > the keyboard opens, the positioning is all wonky, the target text field > sometimes ends up under the action button, etc) > - there were other input issues (switching to the special email-address > keyboard doesn't work) > - problems with the horizontal scrolling between dives (very uneven look > and feel at times) > > That's off the top of my head, six months after I stopped spending time on > this. some of them look like qml/qtquickcontrols issues, some of them our issues the one i'm more positive i's our issue is the positioning of the keyboard and text area, which I added in our bug tracker myself: https://bugs.kde.org/show_bug.cgi?id=375438 > > Yes, I posted about this a couple of days ago, but based on what you say > in this email I don't think that's the right approach because I thought I > had to switch to Controls.2 everywhere - and that's what really causes > most of the pain. will take a look, maybe not too much is missing -- Marco Martin _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
