View - Panes - Review

The Review pane shows conflicts arising from concurrent multi-user editing of linked drawings, displaying the Manifold object ID of each conflicted object and the conflict, with area, line or point in the Type column indicating an editing conflict. The Review pane works when editing drawings or drawing layers in maps.


To use the Review pane, we must have Enterprise Edition and have also specified a version column in the database table to which the drawing has been linked. In addition, the Edit Mode of the drawing in the Link / Share Status dialog must have been set to Review changes made by others (the default when a version column has been specified). See the Multi-User Editing of Linked Drawings topic for details.




Click on a conflict to highlight it. The Review pane's toolbar commands will then apply to that component. The drawing window will show the local version of each object conflict in blue and the remote version in red (colors may be set in the Tools - Options dialog). The easiest way to remember the colors is to think that we are always right (of course!) so that changes made by other users are shown in an alarming, red color.




The local version is the object as we have edited it in our project. The remote version is the object as someone else has edited it.





Center - A "go to" command to center that conflict in the drawing window.


Zoom - Zoom the drawing so that the conflict is completely visible.


Use Local - Commit local changes and update the database to use the local version of the object for the highlighted conflict. Discard changes made by others.


Use All Local - Commit local changes and update the database to use the local version of the object for all conflicts. Discard changes made by others.


Use Remote - Discard local changes and update the database to use the remote version of the object for the highlighted conflict. Download remote changes into the local drawing.


Use All Remote - Discard local changes and update the database to use the remote version of the object for all conflicts. Download remote changes into the local drawing.


View Conflict - Enable (that is, press in, the default setting) to show conflicts in the drawing window using red color and blue color for object geometry and server formatting or local formatting for format conflicts . When not enabled, object conflicts will not be previewed in the drawing window.

(Conflicts pane)

A list of editing conflicts and their types detected from editing changes made by other users which conflict with editing changes we make.

Conflict - Either the object ID for editing conflicts involving the metric of objects or the name of the formatting characteristic for a formatting conflict.

Type - Either Area, Line or Point for editing conflicts to indicate the type of object involved or Format to indicate a formatting conflict.

(status bar)

A text line at the bottom of the dialog indicating the number of editing conflicts.




When presented with a list of conflicts we normally highlight each in turn and then use Center and Zoom to bring each conflict into view in the drawing window. Based on what we see we then decide to use either the local version or the remote version of the object.


If we are feeling particularly authoritative, we can force usage of our edits for all conflicts by choosing the Use All Local command. Conversely, if we think everyone else's edits are to be preferred to ours we can choose the Use All Remote command. Either of these commands should be used with care.


Projects may contain many linked drawings, which could be linked from different data sources. The Review pane will show conflicts for whatever drawing window or drawing layer has the focus.


Reviewing Formatting Conflicts


If the Administrator Console has been used to enable formatting storage on the database server for a linked drawing then linked drawings will show formatting when they are linked into a project and any changes in formatting will be saved back to the database.


Different users can edit the same linked drawing at the same time. If formatting is enabled, different users can change formatting at the same time. Whenever a user changes formatting the new formatting is immediately sent back to the database. Other users working with that same linked drawing will see those formatting changes when they refresh data.


It's a good idea, therefore, to do a Refresh Data command for a linked drawing before changing formatting, to see if someone else has already made any formatting changes not yet displayed. However, even if we do a Refresh Data command it is possible that someone else changes formatting while we are in the process of making formatting changes ourselves and that the other person accomplishes their changes ahead of ours. In that case, an editing conflict will occur. The Review pane will display editing conflicts over formatting and can be used to resolve them.


Selecting an editing conflict with formatting data in the Review pane previews the server version of the formatting in drawing, map and theme windows (the server version of the formatting is applied on top of whatever formatting has been specified locally, to make the difference between formatting as saved on the server and local formatting more noticeable).




In this example we consider formatting changes made to the same linked drawing on two different systems. The drawing used is a version of the US Main sample drawing that has been exported into an Oracle database. The drawing has had formatting storage enabled through the use of Administrator Console. The systems are known as the Blue system and the Green system, from the color of the different Windows XP color schemes used on the different systems.




On the Blue system we open the linked drawing as seen above. The drawing uses a thematic format based upon a Color field to color states in the US. California has a pink color because pink color has been assigned in the thematic format for use with the value in the Color field associated with California.




On the Green system we also open the linked drawing as seen above. Because formatting has been enabled in the Oracle database, whenever we link this drawing into a project it will show the formatting stored with the drawing.




Let's go back to the Blue system and change the thematic format.




We will click into the area background color well (the thematic formatting is used for area background color) to launch the thematic formatting dialog. We then click into the pink color well to change the color.




We will change it to a pastel shade of blue-green.




When we press OK in the thematic formatting dialog the drawing will show the new formatting and the change in the thematic format will be automatically uploaded into the database.


It is important for beginners not to get confused over the subtle, but very significant, difference between a thematic format, which specifies formatting, and values of data attributes in a drawing's table that are used by that thematic format. Changing the color used by a thematic format as seen above is a change in formatting. Changing a data attribute in a drawing's table is just changing a data attribute, not changing formatting, even though as a result of following the formatting in force it may change the color of a particular object being displayed.


Suppose, for example, that we decided to change the color of the state of California by double-clicking into the drawing onto the California area object to change the value of the Color field for that area. We can see from the screen shots above that pink color had been assigned to a Color value of 1 and gray color had been assigned to a Color value of 3. Had we double-clicked into California and change the Color value from 1 to 3 that would have changed the color used to display the state to gray.


However, that would not have changed the formatting because the thematic format defined for that drawing would still be the same: objects with a Color field of 1 would continue to be drawn in pink and objects with a Color field of 3 would continue to be drawn in gray. It is just that the mix of values for Color for different objects would have changed.


When data attributes in tables are changed for linked drawings those changes are immediately communicated into the database and are not subject to review or resolution as are editing changes in object geometry or in formatting. This is conceptually a difference from the way editing changes in geometry or formatting are handled, but it is the long-standing tradition in multiuser database work to do it that way.


Let's get back to the main theme of this example, the change in formatting done on the Blue system and what effect it has, if any, on the Green system.




Back on the Green system, as seen above, we can see that the formatting changes made in the Blue system do not appear. They will not appear until we do a Refresh Data to synchronize the local display with whatever is already on the server. Suppose we do not do a refresh, but instead go ahead and make formatting changes on the Green system?




If we open thematic formatting for area background color on the Green system we see that the color well for a Color value of 1 is still pink. We click into it to change the color.




Let's change the color to a pastel shade of purple and then click OK.




As expected, the color of all areas with a Color value of 1 changes to purple. The Review pane will show a formatting conflict.




We will rearrange our screenshot to show both the Review pane and the drawing window as seen above. Note that the Review pane shows a Format conflict for Area Background. By default, the Review pane shows all conflicts. Until a particular conflict is highlighted, the local display will show local formatting. When we click onto a conflict to highlight the display will show what the version on the server looks like.




When we highlight the conflict the display changes to show the formatting stored on the server, which was set by the user on the Blue system. We can switch back and forth between display of server formatting and local formatting by pressing the View Conflict button to enable or disable it.




With the View Conflict button popped out the display will show local formatting. To make a choice between use of server formatting or local formatting we can press one of the Use.. buttons.




For example, pressing the Use Local button tells Manifold to resolve the formatting conflict by choosing the local formatting and uploading that into the server to override what was placed there by the user on the Blue system.




This resolves the editing conflict by making the server version the same as the local version. The Review pane now no longer shows any editing conflicts.


Note that if we were to now go to the Blue system we would still see the (now obsolete) formatting using pastel blue-green color until we do a Refresh Data command to update the display.


See Also


Multi-User Editing of Linked Drawings

View - Properties - Link / Share Status