aboutsummaryrefslogtreecommitdiffstats
path: root/.github
diff options
context:
space:
mode:
authorGravatar Jan Mulder <jlmulder@xs4all.nl>2018-02-21 09:04:58 +0100
committerGravatar Dirk Hohndel <dirk@hohndel.org>2018-02-24 11:39:49 -0800
commit76a7c860f1d704eba1def0ebf1f23f7a924562ff (patch)
tree8b9c2be36d7d754e88c9a5d3f6370cd495dc4442 /.github
parentcd0b911fe8e7f2c6a374ad100fda429032bea520 (diff)
downloadsubsurface-76a7c860f1d704eba1def0ebf1f23f7a924562ff.tar.gz
Mobile QML UI: wideScreen property change
See also 15cdcdbc6. There, we introduced the wideScreen (set to true) to evade a (cosmetic) bug in (most likely) Kirigami. The top dive was partially obscured on the start of the app. And by setting the wideScreen to true, the application header became of a fixed height. Numerous changes further in Kirigami, we can now set this property to false. This results in a correctly displayed divelist at the start of the app, and *also* an application header that correcly hides itself when scrolling up, and displays itself again when scrolling down. So, a behavior that is common to, for example, mobile brouwsers. This all said. I still believe this is a workround for strange behavior. In fact, we should not need to set this wideScreen property at all, and Kirigami should behave correct in all cases (true, false, unset at our end). It behaves correctly when set to true or false, but still displays a partially hidden top item in the dive list when unset. Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
Diffstat (limited to '.github')
0 files changed, 0 insertions, 0 deletions