-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[App] Do not instantiate dummy QCoreApplication object (fixes #3714) #2491
Conversation
c3ad660
to
e850efd
Compare
e850efd
to
5f9758b
Compare
@m-kuhn I added the doxymentation and since the rebase somehow kicked your comment out of the thread I just give you this hint. |
@wonder-sk assigning you as the original author of https://hub.qgis.org/issues/3714 |
8b0c446
to
3bc53f9
Compare
3bc53f9
to
bb620d4
Compare
bb620d4
to
337c141
Compare
@wonder-sk |
New variables for: - @qgis_os_name: eg 'linux','windows' or 'osx' - @qgis_platform: eg 'desktop' or 'server' - @user_account_name: current user's operating system account name - @user_full_name: current user's name from os account (if available) Sponsored by Andreas Neumann
337c141
to
95708ac
Compare
Agreed with @wonder-sk to postpone this PR until QGIS 3.0, where the whole startup process will be reviewed. |
@wonder-sk I would like to close this PR. You don't need it as a reminder, do you? |
Closing this PR because it will be solved in QGIS 3.0 in a different way. |
This PR separates the instantiation of the
QgsApplication
object and the call toQgsApplication.init()
thereby allowing to do the instantiation earlier in the initialization process and removing the need for a dummyQCoreApplication
object.By doing this all commandline arguments relevant for
QApplication
(e.g. -reverse) are hidden from QGIS and no warnings about unknownargumentslayers are produced.I am not a
QApplication
specialist, so could someone please verify that this does not have any unwanted side effects?