Studio public preview 22.10 also seems to have retained this bug/feature.
It makes the annonations set on the highest sequence redundant. In my opinion, this is more a bug than a feature. I understand that StudioX may have such a UI, but forcing it into Studio which has a large number of users from before to me is not a good design choice.
That would mean all the hardwork documenting what each workflow does must be repeated all over again for each project and we need to change our templates to adjust to a bug/feature? That’s not a valid alternative.
In that case the additional options when you right click (show/hide annotations) are also redundant. Why have those options at all?
I do believe this was rushed before analyzing the impact. Studio is not StudioX. I really hope this is reconsidered.
There is another reason some of us like using sequences (you can debug a sequence consisting of many activities) by using right click and “test activity”.
Containers allow this debugging options, if containers are removed and only activities are to be used, test activity will also be deprived of its main advantage.
Hello all. I am using Studio X.
I had this problem, with the main container, right from beginning.
And all the examples from tutorials was using a Sequence activity.
Instead of this Sequence, I had successfuly used a Group activity.
I just renamed the Group into Sequence in the Properties palette.
And I can say, it worked for me the same like an usual Sequence.
This is a possibility, for people, who are get used with Sequence.
@Dennis0@alexandretperez@postwick and @Adrian_Brinas closing this thread. Below is the screenshot of settings page where the container sequence can be toggled on or off. The show and hide annotations (on right click) also work as expected within studio when the Hide Sequence is set to No.