Details
- Reviewers
nienhueser - Group Reviewers
Marble
Diff Detail
- Repository
- R34 Marble
- Branch
- master
- Lint
No Linters Available - Unit
No Unit Test Coverage
Nice start :-) I guess that's a successful liftoff for our rocket!
src/lib/marble/PluginManager.cpp | ||
---|---|---|
290 | Do we really want a QMessageBox here or would we rather want an OSD message? |
src/lib/marble/PluginManager.cpp | ||
---|---|---|
286 | .isEmpty() |
Didn't know about isEmpty(), but should have, I feel bad now...
If by OSD you mean the notifications from KDE, I don't think it is necessary: Unix users can always look at the debug output, just Windows users would have to debug the application to get those messages, so that's why a QMessageBox is better for them I figure.
I don't think that's necessary. The situation we address here is a broken installation, mostly meant to notify 3rd party developers or packagers about serious problems in the installed files.
- Used isEmpty() instead of testing for equality with empty string.
Just changed the if condition to use isEmpty() instead of a explicit check against an empty string.