**** BEGIN LOGGING AT Sun Mar 13 02:59:58 2016 Mar 13 04:01:03 Sorry, ka6sox, morphis and Tofee, one of you relied to me, but my devices all have been rebooted since then. My username on Github is “DougReeder”. Mar 13 05:53:50 DougReeder: Only ka6sox, scoutcamper, morphis & JaMa can set that up. Tofe & myself don't have access to that :P Mar 13 05:54:44 At least AFAIK, there might be more but me and Tofe for sure not ;) Mar 13 06:16:17 nope, I dont have access to that Mar 13 06:19:42 DougReeder, ping? Mar 13 06:21:31 ka6sox: Can you add DougReeder to https://github.com/orgs/webOS-ports/teams/apps Mar 13 06:22:33 he is invited to be a member of the organization..he has but to accept Mar 13 06:23:16 ka6sox: thnx Mar 13 06:23:21 np Mar 13 11:20:32 Tofe: ping Mar 13 11:34:24 Herrie: pong Mar 13 11:48:23 Tofe: Any idea how to get the bluetooth indicator to behave? It needs to have 3 different states: powered (which it's fixed now) by https://github.com/webOS-ports/luna-next-cardshell/blob/master/qml/StatusBar/Indicators/BluetoothIndicator.qml#l26, connecting and connected which is determined by https://github.com/webOS-ports/luna-next-cardshell/blob/master/qml/StatusBar/SystemMenu/Blueto Mar 13 11:48:23 othElement.qml Mar 13 11:52:31 Tofe: I guess I more or less probably have something working for powered & connected, just not sure how to do the connecting one Mar 13 11:57:36 I would add the source for the image here https://github.com/webOS-ports/luna-next-cardshell/blob/master/qml/StatusBar/SystemIndicators.qml#l104and determine the value based on BluetoothService.powered & BluetoothService.connected Mar 13 11:57:44 But that wouldn't solve the connecting status Mar 13 12:36:49 Herrie: let me have a little look Mar 13 12:48:27 Herrie: would this work ? https://github.com/webOS-ports/luna-next-cardshell/pull/264 Mar 13 14:13:50 Tofe: Sorry just got back from weekly groceries ;) Mar 13 14:13:58 Was nice weather so took a little detour LOL Mar 13 14:14:42 Tofe: Not sure if isTurningOn is the same as Connecting ;) Mar 13 14:14:48 I couldn't figure that out.... Mar 13 14:18:31 Let me just test it :) Mar 13 14:18:44 At least 2 states is an improvement over 1 ;) Mar 13 14:46:50 Herrie: well, it's the only things plausible I saw in the Service Mar 13 17:21:50 Tofe: problem is we connect from Settings app and it doesn't seem to realtime update LNC Mar 13 17:21:58 I guess the BT plugin might need some work?> Mar 13 17:34:32 nizovn: You have any ideas on the indicator for BT? Mar 13 17:38:43 Herrie: so BluetoothService.connected doesn't work? Mar 13 17:43:04 nizovn: I'm pretty sure the WiFiManager and BluetoothManager onenabled and ondisabled events are never fired. Mar 13 17:43:21 nizovn: Perhaps there is a common underlying cause? Mar 13 17:47:44 nizovn: I guess not when we connect from settings Mar 13 17:47:48 Or teh image doesn't update Mar 13 17:48:08 Need to see if Bluetooth is in connectionmanager somehow Mar 13 17:48:14 And if it returns something Mar 13 17:48:27 So we can have a callback and update when something changes Mar 13 17:51:59 elvispre: they should work.. Mar 13 17:55:32 nizovn: Easy to demonstrate: Enable and disable Bluetooth in Settings. See that reflected in the system menu. Try it the other way round (while Settings is already running). Nothing happens. Mar 13 17:58:43 elvispre: ah, right Mar 13 17:58:58 Similar, with WiFi. Mar 13 17:59:14 Of course, I might have them hooked up wrongly in Settings. Mar 13 18:00:48 yes, the problems are in plugins, as setPowered is called only on initialization Mar 13 19:16:22 I didn't fully follow the discussion, but where does the problem seem to be? Mar 13 19:16:51 the managers don't fire events? Mar 13 19:18:28 yes, this is the problem with settings app Mar 13 19:18:37 not sure what's wrong with indicators Mar 13 19:32:47 Well, the indicators only listen **** ENDING LOGGING AT Mon Mar 14 02:59:58 2016