Return updated custom component with ports changed as per change If a port is deleted any corresponding connections must be deleted to keep the CanvasState consistent. That is done elsewhere, since deleting not fully connected connections is a straightforward operation on CanvasState, as done by deleteIncompleteConnections

Return canvasState updated with bad connections that have lost either of their connecting components deleted

Every instance of the current sheet, with the signature it has and the one it should have. An instance's bindings are expressions in the parameters of the sheet it SITS ON - and may be overridden there by a CustomCompParam slot, exactly as in elaboration - so the parent sheet is where they are evaluated. ParameterAnalysis.instanceBindingExprs is the same merge the properties pane and the simulator make.

The instances of the current sheet that no longer match what their own bindings give them.

Whether one instance is out of step with what its own bindings give it: it has a port the sheet does not, lacks one the sheet has, or holds one at the wrong width. The ORDER of the ports is deliberately not compared. An instance's ports are matched to the sheet's Input and Output components by LABEL - by FastCreate when a simulation is elaborated, by SynchronousUtils, and by CanvasStateAnalyser.checkCustomComponentForOkIOs, which compares sets when it decides whether a design is legal - and each port is drawn where the symbol's own saved PortOrder puts it, keyed by port id. So an instance whose ports are in a different order from the sheet's is a correct instance, and reordering it would change nothing that can be seen or simulated. Requiring the orders to match raised this dialog on four of the five shipped demos, whose instances were placed before the I/O components were moved about on their sheets, and described the difference as a width change - which is what the dialog says when nothing structural happened.

compare two I/O signature lists

Change the items x in lst where uPred x with x -> uFunc x. Useful to replace one item of a list

Every sheet has just been written to disk from memory, so none of them has unsaved changes. updateInstance flags each sheet it changes so that the change reaches disk; once it has, the flag has done its job. Left set it made every later "close without saving?" dialog name sheets whose files were already correct, and left the user no way to clear it: the Save button follows the OPEN sheet alone, and an instance is by construction never on that sheet.

returns a popup function to show the dependents update dialog if this is needed this dialog drives all subsequent work changing custom component instances

What the user is being asked to confirm, gathered from every out-of-date instance: the ports that came and went, and which instances change only in width. The structural changes are taken over all instances rather than from a representative one. Instances of a parameterised sheet may be at different widths, so a rename can be guessed for one and not for another; the union is what the sheet's ports actually did.

Save any changed sheets to disk in the project directory

Bring every one of these instances to the signature its own parameter bindings give it.

Bring one instance to the signature its own parameter bindings give it.

Return new model with project updated as per update function. If p.LoadedComponents data is changed, for each sheet that is different the sheet will be saved to disk. This function should be used consistently to keep disk and project data correct.