Output Canvas Items on Workspace views / Arch Prep [1] / USACE ABQ 5.11
Bug Number: n/a
Release notes (y/n): no
For Release Nums: 7.1

SEE full report about this completed architectural preparation:
http://cadswes2.colorado.edu/~philw/2017/CoeAbq5p11/ArchPrep1.html

I've completed the architectural preparation for this project, and am ready 
to turn this over to Robynn. (See the CoeAbq5p11-OutCanv1 branch).

My important goals for this work were:

  (1) Breaking out the implementation of the OutputCanvasScene (a 
      QGraphicsScene, in which all the visible QGraphicsItems live) into a 
      delegated class which can be used by both the OutputCanvasScene and 
      WorkspaceGfxScene classes. The new class is OutputCanvasGfxItemMgr 
      (a QObject subclass).

  (2) Actually deploying an instance in each of the three WorkspaceGfxScenes 
      (Simulation, Geospatial, and Accounting).

  (3) Quite a bit of QGraphicsItem life-cycle testing and fixing. (There 
      were a few things that needed to be done). This seems good now.

This is in a very demo-able state. In a model having an Output Canvas (output 
device), the provisional new menu item, Workspace >> "Set Output Canvas...", 
shows an Output Canvas selector popup.

   The picked Output Canvas is associated with the current RiverWare Workspace 
   View.

   Note however that canvas items (teacups and such) are currently using 
   their Output Canvas coordinates -- which show up on the UPPER LEFT of the 
   Simulation and Accounting Views (and god knows where in the Geospacial 
   View).

   This canvas objects are currently deployed on the Workspace in their 
   "active" (configuration editor) state. So they can be dragged and resized, 
   and Flow Lines can be edited (right in the workspace). For a DEMO, also 
   show the Output Canvas VIEWER of the relevant Output Canvas, and play with 
   the canvas items in the workspace -- including editing flow lines. (Robynn 
   will need to hide the output canvas items which we don't currently intent 
   to support in the workspace views).

   An interesting consequence of deploying output canvas items in the 
   workspace views is that they now support multiple-selection (by dragging 
   a rectangle around multiple items) in the workspace.

See the rest of this report at the URL cited above.