In most cases, changes made to the model or view state pretty much immediately reflect in the designer UI, assuming there is a corresponding UI representation for the model item or view state. What I'm doing is using the view state to establish links
(in a Flowchart designer) between activity designers. Normally this works fine. But occasionally, an exception is thrown saying that a connection cannot be made between two points.
In the event of this exception, I can wrap the statement that throws the exception (in my case, EditingScope.Complete) and retry the logic, this time not specifying the connection points and letting the designer's routing algorithm comes up with its own
The problem I'm experience is when I wrap the call (EditingScope.Complete) in a try/catch block that throws the exception and re-do the connection logic, this time not specifying the view state (but still specifying the Next property of a FlowStep,
or True/False property of a FlowDecision, etc using the ModelItem.SetValue method), visually a connection is not made between the activities. But if I manually close the designer and reload it or use the bread crumb navigation to move away from the current
designer and then return, the connections visually appear.
I want to be able to programmatically refresh the UI based on the updated model / view st
View Complete Post