RESOLVED - Make Editing of Processes Source Code Permanent

[jwaters125]

I have moved the majority of the 'Process Icons' that I use to the desktop.  There are several that I would like to modify.  If I edit the ‘Instance Source Code’ for a specific Process using the 'Commit' button these changes are not saved after closing the Process.

When I close the Process icon the edits revert back to the original.  Can these edits be permanent?

Example: Editing of AutomaticBackgroundExtractor Target Image Correction 'Correction:' from None to Subtraction.  Make these edits permanent.

[Juan Conejero]

The source code changes made to an instance icon are always permanent. Just edit the icon's source code again and you'll see your changes.

The changes you apply directly to a process interface (by clicking the Edit Instance Source Code tool button (empty square)) are permanent as long as you don't reset the tool, or load a new instance (e.g. from a process icon), which replaces the previous one.

Dynamic tools such as DBE are slightly different because if you launch it from Process Explorer, the tool will load a default set of parameter values. This is by design. However, you can modify an existing process icon and then launch the process from it. This will load all parameter values from the icon's instance.

[jwaters125]

Its not saved for me. 

Example - DrizzleIntegration Icon is on my desktop.  If I Edit Instance Source Code and go in and change P.enableCFA from false to true then check the Check Mark (Commit) the value gets changed in the open DrizzleIntegration Process.  But if I close DrizzleIntegration 'X' the changes are not saved.

[jwaters125]

OK - resolved...

After I make the edits and Commit I have to create another instance of the desktop icon.

[Juan Conejero]

Each instance is a different and independent, self-contained and self-sufficient object. For example, a DrizzleIntegration icon transports an instance of the DrizzleIntegration process. The DrizzleIntegration tool window also has its own instance of the same process. However, both instances are independent objects. This is part of PixInsight's object-oriented design.