CoreandServices.book - Ocean - Schlumberger

Custom Processes
The process is deactivated when another process is activated. Override
OnDeactivateCore to properly shut down your process. In our example we remove the
toolbar button:
protected override void OnDeactivateCore()
{
base.OnDeactivateCore();
PetrelSystem.Tools.Remove(myButton);
}
}
Step 5 – Optionally Handle Window Modes
To interact with the native Petrel windows, use the window mode properties:
public abstract class Process
{
...
protected virtual IEnumerable WindowModesCore;
public IEnumerable WindowModes { get; }
}
Typically, this list is managed in the process activation and deactivation. For details, see
“Interaction in Petrel Windows” in Volume 3, “Petrel Customization” in Chapter 2, “User
Interface Services.”
Step 6 - Implement Persistence
When your custom UI takes end user input, the Petrel convention is to save the previously
entered values and display them again the next time the process is run. This is so the end
user does not have to re-enter the same inputs over and over again.
Implement persistence for your custom UI with one of these two methods:
• Implementing IIdentifiable
• Serialization
The recommendation is not to persist the UI but to create a simple nested class containing
the pertinent information and persist that instead.
Both methods are described in “IPresentation” in Volume 3, “Petrel Customization” in
Chapter 2, “User Interface Services.”
6-332 Ocean Application Development Framework 2008.1
Schlumberger Private