05-16-2014 04:30 AM
We are using password protected core sequences which call user-defined (open) sequences at some points. Parameter structures are passed to the user sequences. The types of these containers are public, i.e. the user can see these types in the type palettes.
When setting a breakpoint inside the user sequence, the parameters appear with a padlock, i.e. they are password-protected, just like the sequences from which they were passed. The values can be used in the user sequences, so functionality is available, but we would like the user to be able to see the parameters for easier debugging of his own sequences.
Is there a way to pass parameters from a password-protected sequence file so that they do not appear locked? Preferably by reference since some are output parameters.
Best regards
Peter
05-19-2014 08:28 AM
Hi Peter
Normally I would say that protecting this parameter is in the idea of protecting the howl sequence file.
But as you wrote it is a benefit to see this parameter when you debugging.
Is it a workaround for you to copy the parameters into a temporary local variable?
When yes, add your TempLocalVariable before you start debugging.
Add although a statement Locals.YourTemp=Parameters.YourProtectedParameter after every step you want see an update from this parameters.
05-29-2014 12:21 PM
Hi Andreas,
finally got around to do some more testing with this. It turns out that the parameters are locked, if passed by reference, not locked, if passed by value.
This makes sense. When passing by value, the sequence receives a copy which it can regard as its own. When passing by reference, the parameter still belongs to the (password-protected) calling sequence and may well be regarded as protected.
Since only output parameters need to be passed by reference they can be set by the called sequence anyway, so it knows their values.
Thank you for triggering my brain.
Regards
Peter