**** BEGIN LOGGING AT Sun Jul 10 02:59:58 2016 Jul 10 10:18:24 Morning! Jul 10 10:19:23 morning Jul 10 11:01:00 nizovn: not sure if I understand your PR Jul 10 11:01:39 orientationAngle is never unbinded; or did I miss something? Jul 10 11:01:56 it's unbinded on lock Jul 10 11:02:23 ah, line 95 ? Jul 10 11:03:16 https://github.com/webOS-ports/luna-next-cardshell/commit/29a2d2979bc429fb47a7dd75eb1f38c2300e677c#diff-8fbb7193841d8bfaee99d736585f9d6cR420 Jul 10 11:05:49 Why not change __lockedRotationAngle in SystemMenu ? Jul 10 11:10:13 Unbinding orientationAngle just seems not a good idea; it makes it much more difficult to predict its behavior Jul 10 11:11:43 Using additional properties (like __lockedRotationAngle, maybe also another one if we need it) looks more understandable. At least, that's my opinion. Jul 10 11:22:39 yes i agree Jul 10 11:23:51 but we still need this if we care about devices with hw keyboard which can simulate rotation events Jul 10 11:23:58 but we don't? Jul 10 11:37:25 in that case, the setOrientationAngle is called ? Jul 10 11:38:55 I would say that in this use case, we can set locked to true and use __lockedRotationAngle, because I guess the device won't have an orientation sensor Jul 10 11:39:06 or what kind of device are you thinking of? Jul 10 11:42:13 e.g. emulator should react like it received real sensor event (orientation should not be locked)? Jul 10 12:12:01 it would be better to find a way to really simulate the orientation change, rather than hack some "debug" code into the main qml code Jul 10 12:13:02 if it's just a change of a value (i.e. __lockedRotationAngle + lock), it's quite ok, but here it would mean unbinding and rebinding, and eventually introduce bugs Jul 10 12:13:27 ok Jul 10 21:01:53 anyone still working on this ? **** ENDING LOGGING AT Mon Jul 11 02:59:58 2016