In addition to the basic data sharing and collaboration control modules, some example collaborative modules (including source code) are also available in this release.

MSharePointer

This module is an extension of the original pointer module in release 3.5. It can operate in single user mode giving exactly the same functionality as the original. In addition, however, it can also be used in collaborative mode. The picture above shows two views, before and after connection. Connection to the collaborative session is achieved in the same way as for the other COVISA modules, simply pressing the 'Initiate' button. After connection, the standard group number and connection state widgets appear. In collaborative mode, any internally generated geometry is shared with all other collaborators, as well as going into the user's own Render window. Geometry passed in from the collaborative session replaces any current pointer geometry in the Render window. Assuming all collaborators have the same object visible in their Render modules, then the generated pointer object will highlight the same object in all scenes. The pointer module is wired in a loop with the Render module. The output from Render's Pick port is wired into the input port on MSharePointer. The output Pointer geometry port of MSharePointer is wired into Render's Input port. For more information on wiring up collaborative modules see Starting a Collaborative Module. You can control the size and colour of your pointer, so as to distinguish it from pointers generated by other collaborators in the session. To generate Pick events, the Render must be set into the appropriate mode, see here for an explanation.

MShareGraph3D

This example module is an extension to the original Graph3D module. It can be used in single user mode in the same way as the original. Once connected to a collaborative session, using the initiate button, it can be used collaboratively. This module demonstrates how collaboration can be achieved with a different mechanism to that used by MSharePointer. Rather than sharing the internally generated Geometry, it allows shared control of the module's control panel widgets. When one collaborator changes the value of any of the widgets, this change is passed to the MShareGraph3D modules of all the other collaborators. When using the COVISA Server in its store and foreward mode, the current control widget values are automatically sent to a collaborator who joins late. If the session is using the COVISA Server in pass mode, then the Sync Values button (only visible after connection) can be used to pass the current control widget values to all collaborators to ensure that the values are the same. The data for this module can be shared using an MShareLat module to share the input lattice data. For more information on sharing data in a collaborative session, see Step 4 - Sharing Other Datatypes

MShareLatToGeom

This last example is again an extension of an existing module that can be used in either single user or collaborative modes. The module is connected to a session in the same way as any other collaborative module, by pressing the Initiate button. This module implements collaboration differently to both of the two previously described modules. It effectively combines LatToGeom with an MShareLat module. The user can select either a local data source or a remote data source using the Data_Source widget which becomes visible after connection. If a local data source is selected then the module uses the data wired in from its own map, also sending a copy of that data into the collaborative session when it first arrives. If a remote data source is selected, then the module uses the data coming in from the collaborative session. The control panel widgets of each module are completely independent, but can be shared using an MShareParam module. For more information on sharing parameters in a collaborative session, see Step 3 - Starting a Collaborative Module.