AddOn define to specific level (ModeForwarder, ModeHander, CommandHandler)

Hello everyone,

I would like to have your feedback. Would make sense to define addons on a certain level (ModeForwarder, ModeHander, CommandHandler).

Sometimes it makes sense that I can add an AddOn to the CommandHandler or the ModeHandler.

At the  MES@AE objects I have AddOn's, where I want the user to only be able to set them to the ModeHandler or CommandHandler. Today I check this at the StartupParams.otd with an additional code. But this checking is for the programmer maybe too late because he already set it to the CommandHandler and gets the error message (tag) at the Twin-Cat, and it increases the export time of the OES/CPS. 

With a possibility to define addons for certain levels, the programmer would not make the mistake and it could reduce the export time.

What do you think?

Thanks for feedback!

Best reply by nexidator

I don't think you will be able to measure the time it takes to execute this code. That's what I meant with "perceptibly".

About the NxEventListAddon: You are right, I also don't see a usage for it on a CommandHandler. But it works there just as well. So, no, there has never been a requirement to be more restrictive there.

View original
1
7 replies
Resolved