[SOLVED]ConditionSwitch "pl.dp >= num" is completely IGNORED

[johandark]

I defined several Point levels to activate a Conditional. If it´s high, it´s gonna be RED, if it´s Medium, it´s gonna be Blue and if it´s Low, it´s gonna be Yellow.

I´ve got points done this way:

Code: Select all

init python:        
    class PointLocker(object):
        def __init__(self):
            self.dp = 0
            self.np = 0
            self.mp = 0

Code: Select all

            if type == "dp":
                self.dp += num
                renpy.show_screen("Outer_{}Screen".format(type), message)
            elif type == "np":
                self.np += num
                renpy.show_screen("Outer_{}Screen".format(type), message)
            elif type == "mp":
                self.mp += num
                renpy.show_screen("Outer_{}Screen".format(type), message)

Then I did the Conditions of High to Low Levels:

Code: Select all

#Points for level 001 animation.
    
define Points_High = ("pl.dp >= 24") #Higher Points
    
define Points_Med = ("20 <= pl.dp <= 23") #Medium Points

define Points_Low= ("pl.dp <= 19") #Lowest Points

And Finally the Animation Contain:

Code: Select all

    contains: 
        ConditionSwitch(Points_High and Insert, At("ball_red", position01), 
                                    Points_Med and Insert, At("ball_blue", position01), 
                                    Points_Low and Insert, At("ball_yellow", position01),
                                    "True", Null())

The problem comes, when the "$ Insert == True" is completely funtional (Since I have a "$ Expulse == True", that also works), but the "High/Med/Low" Define points ARE COMPLETELY IGNORED.

It always appear the first one that is in top. In this case "ball_red".

WHY?!.. It´s the last thing I need for ConditionSwitch...

Thanks for your help!

[nyaatrap]

Though I don't think conditionswitch in ATL works, because ATL only evaluates values when it's showing or replacing.

To reflect changes in ATL, you'll need to show it again.

[johandark]

Though I don't think conditionswitch in ATL works, because ATL only evaluates values when it's showing or replacing.

To reflect changes in ATL, you'll need to show it again.

I did not understand what you mean :S

[johandark]

To reflect changes in ATL, you'll need to show it again.

Could you please show some example?..

[xela]

Code: Select all

    contains:
        ConditionSwitch(Points_High and Insert, At("ball_red", position01),
                                    Points_Med and Insert, At("ball_blue", position01),
                                    Points_Low and Insert, At("ball_yellow", position01),
                                    "True", Null())

This is getting a tad ridiculous, how much trouble can one person have figuring out booleans and evaluations...

Try:

Code: Select all

    contains:
        ConditionSwitch(Points_High + " and Insert", At("ball_red", position01),
                              ...

conditions should be strings so they can be converted to bytecode and evaluated on interactions to update the displayable, what you have there will be evaluated at runtime and result in True/False which will remain constant until the displayable is instantiated again.

[johandark]

This is getting a tad ridiculous, how much trouble can one person have figuring out booleans and evaluations....

Yes, You´re right, I´m a completely noob on programming, sorry for troubles...

But thank you very much, Now I learned a new thing and it works perfectly!

Thanks!

[xela]

Yes, You´re right, I´m a completely noob on programming, sorry for troubles...

No trouble on my side, point was that this issue is covered in the docs and even if you don't understand them, this was explained in your previous thread.

But thank you very much, Now I learned a new thing and it works perfectly!

Thanks!

You're welcome