| Summary: | Krazy thinks QMessageBox is a Qt4 class | ||
|---|---|---|---|
| Product: | [Developer tools] krazy | Reporter: | Elvis Angelaccio <elvis.angelaccio> |
| Component: | general | Assignee: | Allen Winter <winter> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Elvis Angelaccio
2016-11-09 14:27:53 UTC
is this a matter of the explanation string being wrong or that we are ok using QMessageBox in some cases instead of KMessageBox? last I knew, we should be using KMessageBox over QMessageBox in KDE applications. (In reply to Allen Winter from comment #1) > is this a matter of the explanation string being wrong or that we are ok > using QMessageBox in some cases instead of KMessageBox? > > last I knew, we should be using KMessageBox over QMessageBox in KDE > applications. Right, this is more about the warning message (since it's not a Qt4 class). Now that I think about it, if we still have KMessagebox there must be a reason and we should probably use it. So it makes sense that krazy looks for this. Title changed to better describe the report. |