Venus 4 vs Venus 6

Hamilton (Venus)
1

Hi everyone, when writing sequences/variables in Venus 6, unlike Venus 4 we have to always declare the sequence as global if not we will not be able to use it in a new sub-method. Venus 4 did this automatically, is there away to change this in Venus 6?

1 Like
2

Hi @fireck,

There haven’t been any changes to sequence declaration, scoping, handling, etc. between VENUS versions 4 and 6. A couple suggestions of things to look at:

  1. Make sure that you’re declaring the sequences within the Main tab of the method, which will automatically assign them the scope of Task-local. Task-local variables are visible across all submethods and the Main tab of a Method (similar to Global). If a variable/sequence/etc. is declared while a submethod is selected, then it will automatically be assigned the Local scope, leaving it only visible/usable within that submethod without the use of parameters. If you declare a variable/sequence/etc. within a submethod and want to quickly change the scope to Task-local, then right-click on the submethod tab of interest and select “Export Local Variables” from the drop-down. A window will pop up with all Local values that can be changed. Check the ones of interest and click Export, which will close the window and move the selected values to the Task-local scope.

    {97A4C726-50AD-4B19-900B-D0FA8B346EAE}
    {97A4C726-50AD-4B19-900B-D0FA8B346EAE}245Ă—191 2.82 KB

    {98AE61C6-C43B-4574-BA0B-5AF449475A00}
    {98AE61C6-C43B-4574-BA0B-5AF449475A00}542Ă—141 5.35 KB

  2. If you’re trying to pass a sequence into a submethod, make sure the parameter for said submethod is set to use Sequence as its type. By default, parameter Type is set to Variable, and when programming quickly it is easy to forget to change this. Also consider the direction for the parameter.
    {3B448373-0658-4D3B-AA7B-AD29E39C46CF}

  3. Check the sequence names for any difficult to interpret characters, such as lower-case “L” and upper-case “i”. Also check for other usage of upper and lower case letters in the sequence name.

  4. If you’re noticing the issue at runtime, then confirm proper resetting of sequence position between uses of the sequence, proper Direction settings in the submethod parameters, and ensure that there aren’t two sequences with the same name across scopes (i.e. one sequence in Local one in Task-local, as the former will mask the latter).

Note that sequences made in the Deck Layout are always assigned the Global scope. If you continue to have issue with your sequences, upload a package file of your method along with directions to where the issue is occurring and I will review.

Thank you,
Dan

4 Likes
3

Thank you

2 Likes
4

I confirm, no change for me.

Best

1 Like