* #585 create new method to set max file size for DataRecordGroups. Needs testing and DRD interface function
* #585 dre implementation and other improvements, needs more work
* #585 update dre, add intf for drd max size functions. Still requires better comments, wiki updates, some refactoring, and testing
* #585 refactor trick-dre
* format trick-dre
* improve readability of dre output for set_max_file_size
Made changes to the command to get the java version to make it
compatible with the mac. Also snuck in my perl script to parse
out the version.
____ _ _ _ _____
| _ \ ___ _ __| | || | | ____|_ _____ _ __
| |_) / _ \ '__| | || |_| _| \ \ / / _ \ '__|
| __/ __/ | | |__ _| |___ \ V / __/ |
|_| \___|_| |_| |_| |_____| \_/ \___|_|
Restore previous size of Variable Tree and Search Panel when visibility
is restored.
Save/restore visibility across sessions.
Add mnemonics and tooltips to menu items.
Ensure the Variable Tree is visible as part of the "Expand Parent in
Tree" actions.
Remove calls to setOneTouchExpandable.
Refs #415
This currently doesn't work 100% properly. It will toggle fine, but when showing the panels it starts them collapsed. Resizing the pane causes them to appear for some reason.
* Values that return "-nan" will now properly show <NaN> in the Trick View variable table.
* +-NaN and +-Infinity are now correctly represented in Trick View.
This solution now handles +- infinity and +-nan instead of just -nan.
* Lifted fix logic into a protected function in the super class.
Removed author/date information.
Put duplicate code from VSFLoat and VSDouble into VSValue.
Added support for -NaN.
* Capped the maximum throttle value to 1000.
Entering extremely large values into the maximum value field of the throttle GUI caused the GUI to freeze. Imposing a cap of 1000 to the maximum value prevents the GUI from freezing.
* Updated brace style from Allman to K&R.
One of the constructor parameters enables automatic creation of
SI-prefixed versions of the root unit, which obviates the need to
create them individually.
Refs #345
The use of True/False prevents the plotting of booleans, as those values
cannot be parsed as doubles. While it's conceptually more pleasing to
use the actual Python keywords for booleans, numbers will work just as
well and allow plotting. #337
