ui.labelSecure->setText(map["secure"].toBool() ? tr("Yes") : tr("No"));
auto features = Quassel::Features{map["featureList"].toStringList(), static_cast<Quassel::LegacyFeatures>(map["features"].toUInt())};
- ui.disconnectButton->setVisible(features.isEnabled(Quassel::Feature::RemoteDisconnect));
+ if (features.isEnabled(Quassel::Feature::RemoteDisconnect)) {
+ // Both client and core support it, enable the button
+ ui.disconnectButton->setEnabled(true);
+ ui.disconnectButton->setToolTip(tr("End the client's session, disconnecting it"));
+ } else {
+ // For any active sessions to be displayed, the core must support this feature. We can
+ // assume the client doesn't support being remotely disconnected.
+ //
+ // (During the development of 0.13, there was a period of time where active sessions existed
+ // but did not provide the disconnect option. We can overlook this.)
+
+ // Either core or client doesn't support it, disable the option
+ ui.disconnectButton->setEnabled(false);
+ // Assuming the client lacks support, set the tooltip accordingly
+ ui.disconnectButton->setToolTip(
+ QString("<p>%1</p><p><b>%2</b></p>").arg(
+ tr("End the client's session, disconnecting it"),
+ tr("This client does not support being remotely disconnected")));
+ }
bool success = false;
_peerId = map["id"].toInt(&success);
void CoreSessionWidget::disconnectClicked()
{
+ // Don't allow the End Session button to be spammed; Quassel's protocol isn't lossy and it
+ // should reach the destination eventually...
+ ui.disconnectButton->setEnabled(false);
+ ui.disconnectButton->setText(tr("Ending session..."));
+
emit disconnectClicked(_peerId);
}