-
Notifications
You must be signed in to change notification settings - Fork 277
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
Customizable layouts - fully functional #278
Conversation
Signed-off-by: Louise Poubel <[email protected]>
Signed-off-by: Louise Poubel <[email protected]>
Codecov Report
@@ Coverage Diff @@
## ign-gazebo2 #278 +/- ##
===============================================
- Coverage 82.33% 78.16% -4.17%
===============================================
Files 172 183 +11
Lines 9304 9917 +613
===============================================
+ Hits 7660 7752 +92
- Misses 1644 2165 +521
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a great change! @chapulina and I were already talking about how to propagate the default gui.config
to the users that have an existing file already. I can't think of a perfect way to do it. Maybe my only suggestion is to tweak the tutorial adding a note in this section:
If you ever want to restore default settings, just delete that file, and the
next time Gazebo is started a new file will be created with default values:
rm $HOME/.ignition/gazebo/gui.config
to reflect that another reason for removing this file might be to receive the updated version of the default configuration.
Signed-off-by: Louise Poubel <[email protected]>
Related to #207
Since this PR we've been able to load GUI configs from the command line with
--gui-config
and default to~/.ignition/gazebo/gui.config
when no<gui>
was specified on SDF.But because of issue #207, we couldn't really reuse configuration files across worlds that have different names. Which meant that the 2 features above couldn't really be used.
This PR, together with gazebosim/gz-gui#104, allow us to remove custom topics and services from SDF files. This means we can rely on the default
gui.config
all the time!More advantages:
See the new tutorial for more info.
rm ~/.ignition/gazebo/gui.config
👇 that's what loading
ign gazebo shapes.sdf
looks like now.Fix
The fix is based on setting the
worldNames
on theMainWindow
so that any plugin can find them. This means that even pureign-gui
plugins likeWorldControl
andWorldStats
can access world names if they want.This is not a solution to #207, but it makes it easier to write GUI plugins that will work with whatever world is currently loaded.
New layout
I tweaked a bit the default
gui.config
file so it includes more plugins. I used a gray background for shapes and transform control because it needs to look ok on both light and dark themes.Deleted lines
I went over all SDF files and:
<topic>
s and<service>
fromWorldControl
andWorldStats
-6 0 6 0 0.5 0
and wasn't loading any plugin that's not ongui.config
, I deleted the entire<gui>
block so the default is used.rolling_shapes
, I moved things so that they work well with the default camera angle.