Using a custom sheet field in a diesel expression.

[Anonymous]

I am trying to add text that changes based on a custom field.   I have been trying to do this by adding a field in mtext and then using a diesel expression to make an if statement. 

I am able to pull a system variable using $(getvar, ) but I can not get diesel to pull custom props.  Is diesel the wrong tool?  is there a better way?

Ex. If oranges (custom field) = 0, I would like the text to say "There are no oranges" if oranges = 1 to 5 I want it to say "There are some oranges"  If oranges > 5 I want it to say "That is too many oranges."  

I am using Autocad LT, it seems like the full version could do this using Rtext, but this may be a limitation on LT.

Any help is appreciated.  Thank you in advance!

[steven-g]

We would need to see a drawing file with examples of these 'oranges' but it does sound to be beyond the capabilities of LT and Diesel. The "IF" function in a Diesel expression is really only for simple yes/no types of testing not for the more complex 'IF CONDITION' then do this or do that. LT isn't designed for this type of 'programming'.

Yes you can get quite complex with Diesel but not easily, it is more for simple toggle switches in a macro.

[Anonymous]

"oranges" is a sheet set custom property. 

Could you use diesel to say "there are oranges"  or "there are no oranges"?

Really my question is, can I call on Sheet Set Custom Properties using diesel?

Once I have the data I can code what I need from there, I am just having problems getting the values from my sheet set properties into diesel.  

I have tried using the Field expression as a variable "%<\AcSm SheetSet.Oranges>%" but this will not call on the value for oranges more than once, then the code breaks.  Any other ideas?

[pendean]

Show us the RTEXT code that could do this, it should work in LT too.

[steven-g · Accepted solution]

I don't think so, you can read the values into a field (which can be used in text) but Diesel can only read variables using getvar and getenv, it cannot read field values or drawing properties, it can also work with strings but only those supplied directly in the code, not with AutoCAD text or mtext strings