Version 2.1

Post date: Nov 9, 2011 11:16:40 PM

• • Version 2.1.3 (not released): This version was never officially released, but the changes here were wrapped into the initial version of Phyplot's successor, DataNav's Figure Composer application.

    • • The color picker popup panel is more compact now, using spinner controls rather than sliders to manually change the R/G/B values. Also fixed a problem with visibility of the R/G/B text field widgets that was seen only in Mac OS X. [These change were made during JMWork development and are inherited by Phyplot, which shares several common libraries with JMWork.]

      • [Windows 2000-specific BUG] For some unknown reason, Phyplot began hanging in some internal Java code implementing the file chooser dialog [more, specifically, in sun.swing.FilePane.ensureFileIsVisible(File f)]. This first happened on 1/25/2008 and only on Hilary's Windows 2000 machine. I was unable to find any mention of this specific bug, and it is unlikely to be properly addressed because Windows 2000 is old. The problem does not occur under the default Java L&F, so I work-around this bug by avoiding the standard Windows L&F whenever the OS platform is Windows 2000.

  • Version 2.1.2, 15 Jan 2008: This version includes two minor tweaks that Steve Lisberger requested.

    • • All child nodes of a graph node are now rendered in the same order that they appear in the child list, whether or not the graph's viewport is clipped. In previous versions, when clipping is turned on, Phyplot would render all non-clipped children first, followed by all trace and function nodes (the only nodes to which clipping applies).

      • [Mac OSX-specific BUG] Opening or saving a figure containing large data sets can take a significant amount of time to complete. While the "glass pane" approach that ignores user input while keeping the UI responsive works under Windows/Linux, it fails to block menu commands under Mac OS X because the "menu bar" is NOT part of the application window. In a previous version, this led to file corruption because a second file I/O operation interfered with a save operation in progress. Fixed -- the program now only allows one file IO background thread to run at a time.

  • Version 2.1.0, 11 Sep 2007: This version includes a number of GUI changes intended to address usage problems that Steve Lisberger and David S were having. It also includes several bug fixes...

    • • Fixed null-pointer exception that prevented display of the Preferences dialog in Mac OS X.

      • Fixed null-pointer exception in model-to-XML conversion of any trace node that was not linked to a data source. This prevented a Phyplot file from being saved correctly and was a serious nuisance!

      • The axes and legend of a graph object now appear at the top of the graph's child list in the Figure Navigator, instead of having their definitions exposed on tabs in the Graph Properties Editor. Of course, the axis and legend objects can neither be created nor removed; they are required elements of a graph. A black line in the child list separates them from all other children of the graph node. To edit an axis or legend, simply place the display focus on the object and use the relevant property editor.

      • Similarly, the tick sets of an axis node are now listed in the axis's child list -- rather than accessing them via a popup dialog from the Axis Properties Editor. An axis can now have any number of child ticks nodes (instead of 0 to 4), and you use the relevant Figure Navigator commands to create/copy/cut/paste/delete tick sets.

      • Extensively tweaked the layout of all Property Editor panels -- particularly WRT eliminating the confusion over which graphic style widgets affect what aspects of an object's rendering (this was especially a problem for the trace and function objects). The integrated HTML help pages were updated to reflect all of the GUI changes made.

      • The stroke color and text/fill color buttons no longer look the same. The former button has a rectangle on its face that is outlined but not filled in the chosen color -- to clarify the fact that it represents the strokeColor property. The latter button, on the other hand, has a filled rectangle.