Dynamic Screen Switch Function

[justinL]

Hi,

I'm trying to find a way to build a "Screen Switch Function" on the fly in an Add-In service. Considering the following configuration:


[AddInExtension("Temp Service", "Service extension description", DefaultStartMode = DefaultStartupModes.Auto)]
public class ProjectServiceExtension : IProjectServiceExtension
{
private IProject _project;



public void Start(IProject context, IBehavior behavior)
{
_project = context;


//-- This can just read from an attached variable on any object, and just execute this
//-- BUT, this throws an exception that says it's a read only setting (Parameter)
//-- Yet, the .Parameters says "get; set;" when I peek at the method implementation in visual studio.
switchFunc.Parameter = "NextScreenName";
switchFunc.Execute();
}
catch(Exception ex)
{
//-- Log exception...
}
}

public void Stop()
{
_project.ScreenCollection.ElementLeftButtonUp -= ScreenCollection_ElementLeftButtonUp;
}
}

My end goal is to just create a little add-on or script to have one common screen switch that can be reused and not have to define a 100 different screen switch functions in my project for simple tasks.

How do I do this in Zenon?

Thanks!

[c.f.]

Seriously, I cannot recommend this. If you want to create a screen switch function every time you create a screen or have a screen switch function created for all your screens: consider to create an Editor wizard or service, which creates the screen switch functions for you.

___

It is possible to change the screen name in a dynamic property.
Example (Wizard):

´´´Code

public void Run(IProject context, IBehavior behavior)
{
var function = context.FunctionCollection["GenericScreenSwitch"];
var propertyPathScreenParameter = "PictSwitch[0].Picture";
var targetScreenName = "Screen2";
function.SetDynamicProperty(propertyPathScreenPara meter,targetScreenName);
function.Execute();
}
´´´End

Also remark, that some of the screen switch functions have filters included. You have to take care of them yourself.

[ursulak]

i'm moving this thread from energy node as the topic is not energy specific

[justinL]

Seriously, I cannot recommend this. If you want to create a screen switch function every time you create a screen or have a screen switch function created for all your screens: consider to create an Editor wizard or service, which creates the screen switch functions for you.



___



It is possible to change the screen name in a dynamic property.

Example (Wizard):



´´´Code



public void Run(IProject context, IBehavior behavior)

{

var function = context.FunctionCollection["GenericScreenSwitch"];

var propertyPathScreenParameter = "PictSwitch[0].Picture";

var targetScreenName = "Screen2";

function.SetDynamicProperty(propertyPathScreenPara meter,targetScreenName);

function.Execute();

}

´´´End



Also remark, that some of the screen switch functions have filters included. You have to take care of them yourself.

Hi C.F.,

I appreciate the help, thank you. It appears that you can't create the function on the fly if it doesn't exist, but it does work if the function already exists, which is no big deal.

The following line of code does not work at runtime:

screenSwitchFunction = context.FunctionCollection.Create("NameOfFunction", FunctionType.ScreenSwitch);

This may be normal behavior though.

You say you do not recommend this, but this is a far more efficient workflow: To have one screen switch function in the project that is reused by each element with the project. Each element would have a simple variable attached that defines the screen name that the triggered element will switch to.

As opposed to having 100 screen switch functions defined in the project for 100 different elements. That's kind of silly when you consider I have to define one screen switch per element and I can't simply create 1 function that simply takes the name of the screen to switch to as the parameter.

Now, that being said, my example is with "Standard" screen types, this may be different when I delve into the intricacies of the other screen types, but for now this is sufficient.

Thanks!

[c.f.]

Yes, the function has to exist.


Creating a function in the context of the runtime does not work. normal behaviour - as stated.