Execution order for UI widgets...

[jbuszkie]

I had a similar issue before and it seemed to work of with a workaround... but now I'm think I have the same issues and I can't get it to do what I want....

I have the something like this..

if (A)
    action (B=false)
        action (C=false)
.
.
.
                      action (F= false)
                            UI (some UI panel)

if (B || C || ....)
 UI (some other UI panel)

it seems like the second if statement get evaluated before all the variable are set in the first chain.

Is there a way to force the whole chain to get executed before the if evalutes the second if?

In my previous delima I used an

if (false)
  text (untitled)

and that fixed my issue.. Not so in this case...

Can I put nested action (REMS) before the if statement like

action ("REM")
   action ("REM")
       action ("REM")
          action ("REM")
.
.
.
                   IF (B || C ||...)  (the second if)

Would that work? (I guess I'll just try it but I'd like to not waste too much time)


Jim

[stanger89]

I may well expose my lack of knowledge about Studio here...

I think the problem is that those variables are made available "upstream". So bascially you set them in the first chain, but since they are children, the second can't see them.

What you want to do is create Attributes for each variable (name A, B, C, etc) and place them at the same level (siblings) of the "if" widgets (or higher if you want them available elsewhere).

[Opus4]

They should be executed in the order they are listed. You show the first If statement as checking A. If that is false, then the entire tree would be skipped before going on to the next If statement. Without seeing actual code, I can't think of anything else at the moment. The variables/attributes also have to be defined at a shared parent location.

- Andy

[jbuszkie]

What you want to do is create Attributes for each variable (name A, B, C, etc) and place them at the same level (siblings) of the "if" widgets (or higher if you want them available elsewhere).

I do have the attibute widets! I just didn't mention that.. :-)

They should be executed in the order they are listed. You show the first If statement as checking A. If that is false, then the entire tree would be skipped before going on to the next If statement. Without seeing actual code, I can't think of anything else at the moment. The variables/attributes also have to be defined at a shared parent location.

- Andy

"A" is true. I have a breakpoint set right below the first "if" I can see it step through all the varaible assignments.. then it jumps right to the UI panel below the second "if". So somehow the second "if" must have gotten evaluated before the the first variable assignment in the first "if".
It's pretty weird..

UhOh... I just found my problem.... I"m a moron I *cough* misspelled *cough* a variable *cough* in my variable assignments *cough*

It works just fine now.. Althought the single step jumps all over the place! But it works.. so I don't really care!


Jim

[nielm]

Originally Posted by Opus4

They should be executed in the order they are listed.

... except that action chains leading to text widgets are executed before action chains leading to other UI widgets, which can cause some out-of-order execution.

You can use your advantafe this by having first an action chain leading to a text widget with an IF (false) parent (so that it does not get shown), being used to calculate A,B,C.. etc, and having attributes A,B,C etc on the top level panel.
The values of A,B,C will then all be set before the rest of the tree is rendered.

See the disk space bar in the title bar for an example,
and also:
this post

[jbuszkie]

Originally Posted by nielm

See the disk space bar in the title bar for an example,
and also:
this post

That was my post the first time I encountered this problem!! That's why I though I understood it! Stupid typo!! Thanks for the help though...

[nielm]

I should read better too I had not realised you had solved your problem!