Ui state persistence

From Buzztard

One task that can be easily implemented is remembering the UI state. Before we need to discuss though which are programm global settings and which properties should be keps with the song.

• main window: size, position, maximized state
  • settings (if at all)
  • song (only if it makes sense to have multiple songs open and we want to arrange them in a certain way)
  • GnomeSession (see [GnomeClient] and [session management])

• active tab (machine view, pattern view, ...)
  • song (/buzztard/setup/properties)

• open machine windows: state, size, position
  • song (/buzztard/setup/machines/<machine>/properties)

• open wire analysis windows: state, size, position
  • song (/buzztard/setup/wires/<wire>/properties)

• machine view: zoom and scrolling position
  • song (/buzztard/setup/properties)

• pattern view: active pattern, cursor pos
  • song (/buzztard/setup/machines/<machine>/patterns/<pattern>/properties) (this is not good yet)

• sequence-view: cursor in sequence, step-filter
  • song (/buzztard/sequence/properties/)
• sequence-view: split pane
  • song (/buzztard/sequence/properties/)

• wavetable-view: split-panes
  • song (/buzztard/wavetable/properties/)

• global/machine windows:
  • interaction controller assignments
    • song (/buzztard/setup/machines/<machine>/interaction-controllers/...)
  • collapsed sections
    • song (/buzztard/setup/machines/<machine>/???)