Bluedevil issueshttps://invent.kde.org/plasma/bluedevil/-/issues2023-11-16T20:03:09Zhttps://invent.kde.org/plasma/bluedevil/-/issues/5What is going on in applet -> listitem's customExpandedViewContent2023-11-16T20:03:09Zivan tkachenkoWhat is going on in applet -> listitem's customExpandedViewContentI am so ever confused by these lines…
https://invent.kde.org/plasma/bluedevil/-/blob/2e21d82a45f054ba9e41679726673a423ea17b58/src/applet/package/contents/ui/DeviceItem.qml#L201-204
```qml
customExpandedViewContent: Component {
...I am so ever confused by these lines…
https://invent.kde.org/plasma/bluedevil/-/blob/2e21d82a45f054ba9e41679726673a423ea17b58/src/applet/package/contents/ui/DeviceItem.qml#L201-204
```qml
customExpandedViewContent: Component {
id: expandedView
// ...
}
// Hide device details when the device for this delegate changes
// This happens eg. when device connects/disconnects
property QtObject __dev
readonly property QtObject dev : Device
onDevChanged: {
if (__dev === dev) {
return;
}
__dev = dev;
if (expandedView.status === Component.Ready) {
expandableListItem.collapse();
expandableListItem.ListView.view.currentIndex = -1;
}
}
```
What does Component's status has to do with anything? And unconditionally resetting `currentIndex` is probably too much in case a user has been interacting with some other list item (device) at this time.https://invent.kde.org/plasma/bluedevil/-/issues/4Daemon destructor is not called during logout2022-10-06T09:31:40ZMikhail VinogradovDaemon destructor is not called during logoutDaemon destructor is not called during logout. In order to reproduce the problem, you need to logout and login again.
[The destructor](https://invent.kde.org/plasma/bluedevil/-/blob/master/src/kded/bluedevildaemon.cpp#L105) will not wor...Daemon destructor is not called during logout. In order to reproduce the problem, you need to logout and login again.
[The destructor](https://invent.kde.org/plasma/bluedevil/-/blob/master/src/kded/bluedevildaemon.cpp#L105) will not work and the system will not save the new state of the monitor. For example, if you set a different bluetooth power state and log out, your state will not change after logging in (with `launchState=remember` config option).
Most likely this is due to calling `kill` instead of `terminate` for the kded modulehttps://invent.kde.org/plasma/bluedevil/-/issues/3Follow-up from "New bluetooth KCM"2020-09-03T10:17:29ZNicolas FellaFollow-up from "New bluetooth KCM"The following discussion from !8 should be addressed:
- [ ] @broulik started a [discussion](https://invent.kde.org/plasma/bluedevil/-/merge_requests/8#note_96877): (+1 comment)
> Does BluezQt not have strings for these? This would...The following discussion from !8 should be addressed:
- [ ] @broulik started a [discussion](https://invent.kde.org/plasma/bluedevil/-/merge_requests/8#note_96877): (+1 comment)
> Does BluezQt not have strings for these? This would duplicate them between KCM and Plasmoid I guess
Look into de-duplicating thingshttps://invent.kde.org/plasma/bluedevil/-/issues/2Follow-up from "New bluetooth KCM"2020-09-03T10:16:42ZNicolas FellaFollow-up from "New bluetooth KCM"The following discussion from !8 should be addressed:
- [ ] @broulik started a [discussion](https://invent.kde.org/plasma/bluedevil/-/merge_requests/8#note_96866): (+3 comments)
> Can we use a `KIO::CommandLauncherJob` here? Assum...The following discussion from !8 should be addressed:
- [ ] @broulik started a [discussion](https://invent.kde.org/plasma/bluedevil/-/merge_requests/8#note_96866): (+3 comments)
> Can we use a `KIO::CommandLauncherJob` here? Assuming there is a desktop file.