Add new comment

I think minimize/maximize would be more useful and what was really requested.
I miss that functionality too.

Something like:

MinimizeMaximize {

  If CurrentSize > MinimumSize {
    setProperty(MaximizeTo = CurrentSize);
    TrackHeight ( MinimumSize );
  }

  If (CurrentSize == MinimumSize) AND PropertyExists(MaximizeTo) {
    TrackHeight ( Property(MaximizeTo) );
  }

  If (CurrentSize == MinimumSize) AND PropertyDoesNotExist(MaximizeTo) {

// Since we can't know what the previous height was,
// since that height could have been reached using keyboard shortcuts, mouse, etc.
// and the user expects it to be maximized, we maximize it to the default height.
// I think that would be acceptable behavior for the user.
// Keeping track height states for all tracks would allow for perfectly accurate behavior,
// but it seems absurd to me to set all that up for such a small feature.

   TrackHeight ( DefaultSize );
  }

}