Skip to content
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

rqt* takes too long to launch #172

Closed
LucidOne opened this issue Sep 2, 2013 · 5 comments
Closed

rqt* takes too long to launch #172

LucidOne opened this issue Sep 2, 2013 · 5 comments
Assignees

Comments

@LucidOne
Copy link

LucidOne commented Sep 2, 2013

Working on .desktop files to be able to launch rqt tools via the GUI.

From a user experience point of view all of the rqt tools take way to long to launch.
Ex: rqt_reconfigure and rqt_bag take about 4.5 seconds to launch.

It looks like rqt needs a splash screen like rviz
https://qt-project.org/doc/qt-4.7/qsplashscreen.html

At the very least .show() the window earlier so users don't keep launching because it looks like nothing happened.

@DorianScholz
Copy link
Member

You can try using the --cache-plugins option to speed it up (maybe this should be default anyway for normal users).
But you're right, it should start/show faster.
At least when you start in standalone mode...

@LucidOne
Copy link
Author

LucidOne commented Sep 2, 2013

--cache brings it down to about 3 seconds, which helps but isn't ideal.

@ablasdel
Copy link
Contributor

ablasdel commented Sep 2, 2013

These three seconds are the time it takes to scan the system for all available plugins correct?

I thought there was an enhancement ticket on rqt proper that requested not scanning for available plugins when in stand alone mode. Can't find it anymore though. Perhaps we should create that?

@DorianScholz
Copy link
Member

if its in cache mode, it should not scan the file system for plugins and only read in the cached info...
but in stand alone mode it should also not scan for other plugins, so if thats not the case, there should be a ticket!
in any case, i think we need to check which part is actually taking how long and then decide which parts are actually necessary for which startup configuration.

@dirk-thomas
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants