Changeset View
Standalone View
src/dolphinmainwindow.cpp
| Show First 20 Lines • Show All 65 Lines • ▼ Show 20 Line(s) | |||||
| 66 | #include <KUrlComboBox> | 66 | #include <KUrlComboBox> | ||
| 67 | #include <KUrlNavigator> | 67 | #include <KUrlNavigator> | ||
| 68 | 68 | | |||
| 69 | #include <QApplication> | 69 | #include <QApplication> | ||
| 70 | #include <QClipboard> | 70 | #include <QClipboard> | ||
| 71 | #include <QCloseEvent> | 71 | #include <QCloseEvent> | ||
| 72 | #include <QDialog> | 72 | #include <QDialog> | ||
| 73 | #include <QFileInfo> | 73 | #include <QFileInfo> | ||
| 74 | #include <QLineEdit> | 74 | #include <QLineEdit> | ||
elvisangelaccio: Not needed? (or at least, I can build without it) | |||||
| 75 | #include <QMenu> | 75 | #include <QMenu> | ||
| 76 | #include <QMenuBar> | 76 | #include <QMenuBar> | ||
| 77 | #include <QPushButton> | 77 | #include <QPushButton> | ||
elvisangelaccio: Not needed? (or at least, I can build without it) | |||||
| 78 | #include <QShowEvent> | 78 | #include <QShowEvent> | ||
| 79 | #include <QStandardPaths> | 79 | #include <QStandardPaths> | ||
| 80 | #include <QTimer> | 80 | #include <QTimer> | ||
| 81 | #include <QToolButton> | 81 | #include <QToolButton> | ||
| 82 | 82 | | |||
| 83 | namespace { | 83 | namespace { | ||
| 84 | // Used for GeneralSettings::version() to determine whether | 84 | // Used for GeneralSettings::version() to determine whether | ||
| 85 | // an updated version of Dolphin is running. | 85 | // an updated version of Dolphin is running. | ||
| ▲ Show 20 Lines • Show All 312 Lines • ▼ Show 20 Line(s) | 393 | if (m_tabWidget->count() > 1 && GeneralSettings::confirmClosingMultipleTabs() && closedByUser) { | |||
| 398 | // QDialogButtonBox::Cancel -> do nothing | 398 | // QDialogButtonBox::Cancel -> do nothing | ||
| 399 | QDialog *dialog = new QDialog(this, Qt::Dialog); | 399 | QDialog *dialog = new QDialog(this, Qt::Dialog); | ||
| 400 | dialog->setWindowTitle(i18nc("@title:window", "Confirmation")); | 400 | dialog->setWindowTitle(i18nc("@title:window", "Confirmation")); | ||
| 401 | dialog->setModal(true); | 401 | dialog->setModal(true); | ||
| 402 | QDialogButtonBox* buttons = new QDialogButtonBox(QDialogButtonBox::Yes | QDialogButtonBox::No | QDialogButtonBox::Cancel); | 402 | QDialogButtonBox* buttons = new QDialogButtonBox(QDialogButtonBox::Yes | QDialogButtonBox::No | QDialogButtonBox::Cancel); | ||
| 403 | KGuiItem::assign(buttons->button(QDialogButtonBox::Yes), KGuiItem(i18nc("@action:button 'Quit Dolphin' button", "&Quit %1", QGuiApplication::applicationDisplayName()), QIcon::fromTheme(QStringLiteral("application-exit")))); | 403 | KGuiItem::assign(buttons->button(QDialogButtonBox::Yes), KGuiItem(i18nc("@action:button 'Quit Dolphin' button", "&Quit %1", QGuiApplication::applicationDisplayName()), QIcon::fromTheme(QStringLiteral("application-exit")))); | ||
| 404 | KGuiItem::assign(buttons->button(QDialogButtonBox::No), KGuiItem(i18n("C&lose Current Tab"), QIcon::fromTheme(QStringLiteral("tab-close")))); | 404 | KGuiItem::assign(buttons->button(QDialogButtonBox::No), KGuiItem(i18n("C&lose Current Tab"), QIcon::fromTheme(QStringLiteral("tab-close")))); | ||
| 405 | KGuiItem::assign(buttons->button(QDialogButtonBox::Cancel), KStandardGuiItem::cancel()); | 405 | KGuiItem::assign(buttons->button(QDialogButtonBox::Cancel), KStandardGuiItem::cancel()); | ||
| 406 | buttons->button(QDialogButtonBox::Yes)->setDefault(true); | 406 | buttons->button(QDialogButtonBox::Yes)->setDefault(true); | ||
@ngraham rominf: @ngraham
How about this? Closing a window with all opened tabs is destructive in my opinion. My… | |||||
Yes, I think it's appropriate to have the cancel button be the default button for this dialog. ngraham: Yes, I think it's appropriate to have the cancel button be the default button for this dialog. | |||||
| 407 | 407 | | |||
| 408 | bool doNotAskAgainCheckboxResult = false; | 408 | bool doNotAskAgainCheckboxResult = false; | ||
| 409 | 409 | | |||
| 410 | const int result = KMessageBox::createKMessageBox(dialog, | 410 | const auto result = KMessageBox::createKMessageBox(dialog, | ||
| 411 | buttons, | 411 | buttons, | ||
| 412 | QMessageBox::Warning, | 412 | QMessageBox::Warning, | ||
| 413 | i18n("You have multiple tabs open in this window, are you sure you want to quit?"), | 413 | i18n("You have multiple tabs open in this window, are you sure you want to quit?"), | ||
| 414 | QStringList(), | 414 | QStringList(), | ||
| 415 | i18n("Do not ask again"), | 415 | i18n("Do not ask again"), | ||
| 416 | &doNotAskAgainCheckboxResult, | 416 | &doNotAskAgainCheckboxResult, | ||
| 417 | KMessageBox::Notify); | 417 | KMessageBox::Notify); | ||
Unrelated change? (At least in Okular there were huge discussions on the type of icon, and I think it's bad form if you just sneak in such changes in this patch…) rkflx: Unrelated change?
(At least in Okular there were huge discussions on the type of icon, and I… | |||||
I thought that making the separate patch because of one line of code is too much. Sorry. Do you agree with the change by itself? Should I do it in the separate patch? rominf: I thought that making the separate patch because of one line of code is too much. Sorry. Do you… | |||||
One-line patches are perfectly fine. In general, keep to one change per patch, and don't try to sneak unrelated changes into patches. ngraham: One-line patches are perfectly fine. In general, keep to one change per patch, and don't try to… | |||||
OK. See D11293. rominf: OK. See D11293. | |||||
rkflx: > Do you agree with the change by itself?
That's for #dolphin to decide. Personally I think… | |||||
Usability-wise, Cancel is the appropriate default. The default button should never cause you to lose work or state. If tab state is considered unimportant, then we shouldn't have a "close multiple tabs" confirmation in the first place. But if we do have one, then the safe/non-destructive choice must be default. ngraham: Usability-wise, {nav Cancel} is the appropriate default. The default button should never cause… | |||||
What you say applies for regular dialogs. However, here we are in a confirmation dialog, where we already saved the user from a destructive action. Now we should present the sensible choice by default, which IMO is quitting. Or do you want another safety net? Anyway, do what you want and talk to Dolphin's maintainers, I don't have time to discuss this right now. Maybe we'll change it back later when this is unified across all apps. rkflx: What you say applies for regular dialogs. However, here we are in a //confirmation// dialog… | |||||
Okay, looking at the new Okular dialog, I'm pretty sure it should work like this:
IOW, window state is less important (but still worth a confirmation) than unsaved user files (which are worth a warning). rkflx: Okay, looking at the new Okular dialog, I'm pretty sure it should work like this:
- "Are you… | |||||
ngraham: Hmm, you make some good points. I'll have a think. | |||||
Cannot edit inline comments, therefore let me clarify:
For unsaved changes, the "Save" action should be default, of course. What I meant here was when you can only choose between losing all work and cancelling. rkflx: Cannot edit inline comments, therefore let me clarify:
> "Discard changes"-type dialog: Cancel… | |||||
+1 elvisangelaccio: > What you say applies for regular dialogs. However, here we are in a confirmation dialog… | |||||
ngraham: OK, you guys have convinced me! Good arguments. | |||||
| 418 | 418 | | |||
| 419 | if (doNotAskAgainCheckboxResult) { | 419 | if (doNotAskAgainCheckboxResult) { | ||
| 420 | GeneralSettings::setConfirmClosingMultipleTabs(false); | 420 | GeneralSettings::setConfirmClosingMultipleTabs(false); | ||
| 421 | } | 421 | } | ||
| 422 | 422 | | |||
| 423 | switch (result) { | 423 | switch (result) { | ||
| 424 | case QDialogButtonBox::Yes: | 424 | case QDialogButtonBox::Yes: | ||
| 425 | // Quit | 425 | // Quit | ||
| 426 | break; | 426 | break; | ||
| 427 | case QDialogButtonBox::No: | 427 | case QDialogButtonBox::No: | ||
| 428 | // Close only the current tab | 428 | // Close only the current tab | ||
| 429 | m_tabWidget->closeTab(); | 429 | m_tabWidget->closeTab(); | ||
| 430 | Q_FALLTHROUGH(); | 430 | Q_FALLTHROUGH(); | ||
| 431 | default: | 431 | default: | ||
| 432 | event->ignore(); | 432 | event->ignore(); | ||
| 433 | return; | 433 | return; | ||
| 434 | } | 434 | } | ||
| 435 | } | 435 | } | ||
| 436 | 436 | | |||
| 437 | if (m_terminalPanel->hasProgramRunning() && GeneralSettings::confirmClosingTerminalRunningProgram() && closedByUser) { | ||||
| 438 | // Ask if the user really wants to quit Dolphin with a program that is still running in the Terminal panel | ||||
In general we try to avoid gendered language where possible, even in a code comment. How about: "Ask if the user really wants to..." ngraham: In general we try to avoid gendered language where possible, even in a code comment. How about… | |||||
| 439 | // Open a confirmation dialog with 3 buttons: | ||||
| 440 | // QDialogButtonBox::Yes -> Quit | ||||
| 441 | // QDialogButtonBox::No -> Show Terminal Panel | ||||
| 442 | // QDialogButtonBox::Cancel -> do nothing | ||||
Can't you use any of KMessageBox's built-in dialogs rather than creating the entire QDialog yourself? broulik: Can't you use any of `KMessageBox`'s built-in dialogs rather than creating the entire `QDialog`… | |||||
I just copy pasted ConfirmClosingMultipleTabs code because that's my first written dialog in KDE and I don't know how the things are done. If you think that this should be changed, then we have to change ConfirmClosingMultipleTabs too. rominf: I just copy pasted `ConfirmClosingMultipleTabs` code because that's my first written dialog in… | |||||
See also T7022: Improve confirmation dialog when closing multiple tabs. TL;DR: Everybody does it differently, in the far future it would be nice to make it consistent across apps. Perhaps I'd keep Dolphin's style here for now, but that's for Dolphin to decide. rkflx: See also {T7022}.
TL;DR: Everybody does it differently, in the far future it would be nice to… | |||||
| 443 | QDialog *dialog = new QDialog(this, Qt::Dialog); | ||||
| 444 | dialog->setWindowTitle(i18nc("@title:window", "Confirmation")); | ||||
| 445 | dialog->setModal(true); | ||||
| 446 | auto standardButtons = QDialogButtonBox::Yes | QDialogButtonBox::Cancel; | ||||
| 447 | if (!m_terminalPanel->isVisible()) { | ||||
| 448 | standardButtons |= QDialogButtonBox::No; | ||||
The Show Terminal Panel button should probably only be displayed if the Terminal panel is hidden. Otherwise it seems odd that it's there, and when you click on it, nothing different appears to happen compared to just hitting the cancel button. ngraham: The {nav Show Terminal Panel} button should probably only be displayed if the Terminal panel is… | |||||
Terminal panel gets focus. I think it's reasonable to keep the button. Your opinion? rominf: > Otherwise it seems odd that it's there, and when you click on it, nothing different appears… | |||||
Regardless, some kind of change is needed, because the button says "Show Terminal Panel", not "Focus Terminal Panel". A button should always do what it says it'll do, or else users learn not to truth the software. If we want to do make it simply focus the Terminal panel when the Terminal panel is open, then the text should change accordingly. ngraham: Regardless, some kind of change is needed, because the button says "Show Terminal Panel", not… | |||||
| 449 | } | ||||
| 450 | QDialogButtonBox *buttons = new QDialogButtonBox(standardButtons); | ||||
A dialog box's default button should never invoke a destructive action. In this context, killing the process is akin to quitting with unsaved changes and should be considered destructive. The button's red icon also provides a hint. :) The Cancel button should be the default button here. ngraham: A dialog box's default button should //never// invoke a destructive action. In this context… | |||||
| 451 | KGuiItem::assign(buttons->button(QDialogButtonBox::Yes), KStandardGuiItem::quit()); | ||||
| 452 | if (!m_terminalPanel->isVisible()) { | ||||
Why another if (!m_terminalPanel->isVisible()) block? Can't we merge this with the one above? elvisangelaccio: Why another `if (!m_terminalPanel->isVisible())` block? Can't we merge this with the one above? | |||||
We actually can't--at least not cleanly. The top block modifies standardButtons, which is consumed later, the product of which (buttons) is needed in the second block. ngraham: We actually can't--at least not cleanly. The top block modifies `standardButtons`, which is… | |||||
| 453 | KGuiItem::assign( | ||||
| 454 | buttons->button(QDialogButtonBox::No), | ||||
Please use const auto result, since this function returns a QDialogButtonBox::StandardButton. elvisangelaccio: Please use `const auto result`, since this function returns a `QDialogButtonBox… | |||||
| 455 | KGuiItem(i18n("Show &Terminal Panel"), QIcon::fromTheme(QStringLiteral("utilities-terminal")))); | ||||
Let's phrase this text in a more standard, grammatically correct manner: "A program is still running in the Terminal panel. Are you sure you want to quit?" Bonus points if we can get the actual running command and display it in the text here somehow. Also +1 for @rkflx's suggestion for a button that will show the terminal panel if it's hidden. ngraham: Let's phrase this text in a more standard, grammatically correct manner:
"A program is still… | |||||
Done your task for bonus points and @rkflx's suggestion. rominf: Done your task for bonus points and @rkflx's suggestion. | |||||
| 456 | } | ||||
| 457 | KGuiItem::assign(buttons->button(QDialogButtonBox::Cancel), KStandardGuiItem::cancel()); | ||||
This is the name of the key that will be stored in settings to remember this. The text in the user interface is always "Do not ask again" broulik: This is the name of the key that will be stored in settings to remember this. The text in the… | |||||
| 458 | | ||||
With the actual program name in the string (thumbs up for that), we need a small change to make it grammatically correct: A program -> The program ngraham: With the actual program name in the string (thumbs up for that), we need a small change to make… | |||||
But it is a default. Why isn't this working? rominf: > but the Cancel button still isn't the default
But it is a default. Why isn't this working? | |||||
Does it work for you? If not, you need to test the changes you're making. As for why, I don't know; it's your patch. :) One of the fun parts of producing a patch is that you often go down the rabbit hole of finding other bugs in the code you're touching! ngraham: Does it work for you? If not, you need to test the changes you're making. As for why, I don't… | |||||
| 459 | bool doNotAskAgainCheckboxResult = false; | ||||
| 460 | | ||||
No word puzzles, please. Let's add the program within the i18n function call using a format string, rather than string concatenation. ngraham: No word puzzles, please. Let's add the program within the `i18n` function call using a format… | |||||
rominf: Sorry, I didn't know that `i18n` works that way. Fixed it. | |||||
| 461 | const auto result = KMessageBox::createKMessageBox( | ||||
| 462 | dialog, | ||||
| 463 | buttons, | ||||
| 464 | QMessageBox::Warning, | ||||
| 465 | i18n("The program '%1' is still running in the Terminal panel. Are you sure you want to quit?", m_terminalPanel->runningProgramName()), | ||||
| 466 | QStringList(), | ||||
| 467 | i18n("Do not ask again"), | ||||
| 468 | &doNotAskAgainCheckboxResult, | ||||
| 469 | KMessageBox::Dangerous); | ||||
| 470 | | ||||
| 471 | if (doNotAskAgainCheckboxResult) { | ||||
| 472 | GeneralSettings::setConfirmClosingTerminalRunningProgram(false); | ||||
| 473 | } | ||||
| 474 | | ||||
| 475 | switch (result) { | ||||
| 476 | case QDialogButtonBox::Yes: | ||||
elvisangelaccio: Missing braces | |||||
| 477 | // Quit | ||||
| 478 | break; | ||||
| 479 | case QDialogButtonBox::No: | ||||
| 480 | actionCollection()->action("show_terminal_panel")->trigger(); | ||||
| 481 | // Do not quit, ignore quit event | ||||
| 482 | Q_FALLTHROUGH(); | ||||
This switch now exists twice in the same function. There must be a smarter way of doing that, right? markg: This switch now exists twice in the same function. There must be a smarter way of doing that… | |||||
That's 2 different switches. Look at case QDialogButtonBox::No: branch. I'm sure it's possible to merge them, but that would hurt readability. rominf: That's 2 different switches. Look at `case QDialogButtonBox::No:` branch. I'm sure it's… | |||||
Right, but this also hurts ;) markg: Right, but this also hurts ;)
Oke, it's a tradeoff i suppose. Readability over duplication. | |||||
elvisangelaccio: Please use `Q_FALLTHROUGH` instead. | |||||
| 483 | default: | ||||
| 484 | event->ignore(); | ||||
| 485 | return; | ||||
| 486 | } | ||||
| 487 | } | ||||
| 488 | | ||||
| 437 | GeneralSettings::setVersion(CurrentDolphinVersion); | 489 | GeneralSettings::setVersion(CurrentDolphinVersion); | ||
| 438 | GeneralSettings::self()->save(); | 490 | GeneralSettings::self()->save(); | ||
| 439 | 491 | | |||
| 440 | KXmlGuiWindow::closeEvent(event); | 492 | KXmlGuiWindow::closeEvent(event); | ||
| 441 | } | 493 | } | ||
| 442 | 494 | | |||
| 443 | void DolphinMainWindow::saveProperties(KConfigGroup& group) | 495 | void DolphinMainWindow::saveProperties(KConfigGroup& group) | ||
| 444 | { | 496 | { | ||
| ▲ Show 20 Lines • Show All 1176 Lines • Show Last 20 Lines | |||||
Not needed? (or at least, I can build without it)