Jump to content

ConditionValue semantic issue


Recommended Posts

Hi,

 

I am trying to specify a "negative" condition, like Lvar not equal 10.5 and I would like to not be obliged to multiply the tests... (<10.5 or >10.5)

 

I tried

- "ConditionValue": "<>10.5"

- "ConditionValue": "!=10.5 "

 

with no luck...

 

And I have an issue with the Configurator which refuse to load some "hand modified" profiles (with no information !), perfectly validated by a json formater AND by the Bridge which load and execute them perfectly...

 

I know I have suppress "useless" parameters like "VariableBoundaries" which are not even initialized by the Configurator....

 

             "VariableBoundaries": {
               "MinValue": "",
                "MaxValue": "",
                "Clamp": false
              }

 

Let me know the mandatory fields for the configurator...

 

Thanks

 

Gérard

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use