Open GoogleCodeExporter opened 9 years ago
It looks like the code exists for this already in atrias_gui.cpp but is
commented out.
Original comment by cmartin....@gmail.com
on 23 Jan 2012 at 9:49
Original comment by cmartin....@gmail.com
on 23 Jan 2012 at 11:52
Should all of the user entered values be saved? There are other settings in
various tabs such as in the Raibert Control tab. This seems like the best user
experience.
Original comment by cmartin....@gmail.com
on 1 Feb 2012 at 11:25
It does seem like a good idea to save all user-entered values. I don't know
for sure if that's the best thing, but I suggest doing whatever you think is
best, and then we will find out whether or not we like it in the near future,
as we begin to use it extensively while running experiments on the robot.
Original comment by jonathan...@gmail.com
on 2 Feb 2012 at 4:57
Since we've been using the GUI a good amount over the past couple days it now
seems like we should have save defaults and restore defaults buttons so that
the GUI doesn't just save the last values you entered when it closes. Instead,
any time while it's running you can save the gains you particularly like for a
given controller by clicking the save defaults button. Then if at any time you
want to go back to those settings, you could click the restore defaults button
and it would reload them from it's save file. We would also want it to
automatically load the saved gain values on start up.
Original comment by kit...@gmail.com
on 8 Feb 2012 at 5:42
I am working it out on paper now. I am planing on making a new file that has a
class which does this functionality.
Original comment by cmartin....@gmail.com
on 9 Feb 2012 at 12:43
Accepting until I can find someone else to add the functionality.
Original comment by yoos117@gmail.com
on 19 Apr 2012 at 7:06
This will be the next major feature that I will add to the GUI. It would have
been included in the first revision of the new GUI but I could not identify a
way to make it work seamlessly. However, I will focus my efforts and find a way.
One possibility would be to have controller libraries have additional functions
for loading and saving GUI values, but I'd like to avoid requiring more
controller-specialized code.
Original comment by broodoo...@gmail.com
on 8 Jun 2012 at 1:30
Original issue reported on code.google.com by
kit...@gmail.com
on 18 Jan 2012 at 10:46