The necessity to define variables of generic datatypes would aid in proper abstraction. For my specific use of PLCnext Engineer, I am abstracting some common logic for functionality we can add for a given system. Ideally, I am able to build all the functionality into one function block using the available libraries.
For the current function block I am building, I have a block inside of my function block which has an input with type ANY(STRUCT). Unless I am able to define generic types from PLCnext Engineer, I will either have to force the user to add repetitive code each time they want to use the feature library OR I am forced to write a library in C#, which is not a great choice given the technical strengths of our team, lending to lacking long term supportability of our feature libraries that are supposed to lighten the load when including already created features in new builds.
Thank you so much for your feedback in advance. Please let me know if I am missing functionality within PLCnext Engineer or confirm that this is in fact a limitation of PLCnext Engineer. Is this a feature that could be implemented if it is not already?
I hope you will find this as a fair critique of a powerful piece of software.