global variable call

[Bobo]

The global declaration of the rollout should be BEFORE the two RC menus if the menus are supposed to "see" the rollout.
If you run the script twice, it will probably start working on any machine, but the trick is to make it run the first time correctly...

[Pjanssen]

Perhaps slightly off topic, but a method I always find useful is putting all the UI things in a struct, so that you can use just one global for all UI elements:

struct myUI (
rcmenu firstRC (
--code here
)

rcmenu secondRC (
--code here
)
)
global myUI = myUI();

With that done, you can call anything inside the structure by using:
myUI.firstRC
--or:
myUI.secondRC

[MoonDoggie]

global rlt_main

rcmenu1 (
// access rollouts with rlt_name.rlt_element like
// rlt_main.btn_Press.width = 200
)

rcmenu2 (
)

rlt_main (
button btn_Press "Press me"
)

[MoonDoggie]

In the above example there is no need for a structure and you accomplish the same thing.

[Hobbs]

Thanks for clearing that up for me :thumbsup:. The struct idea seems like a good thing to implement as well, hadn't thought of that.

[Pjanssen]

In the above example there is no need for a structure and you accomplish the same thing.
True, for a just one or two things that you want to be global it's more simple indeed. For more complex things a structure might be easier, as you can access everything within the structure globally, with just one global variable.

[MoonDoggie]

true, and certainly worth mentioning. Many thanks.

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.