Attribute 0.0 not found

I got some error and the Y placing is not going as I want, what does the attribute 0.0 not found mean?

It makes it easier to help if you can post the model you are working on.

Your If statement is incorrect, should look like this:

=IF(Condition1, Return1, IF(Condition2, Return2, Return3))

I think my IF is correct

=IF(Position=2, AlignX, IF(Position=3,Tuinkamer!A11_TotalWidth-AlignX, IF(Position=1, current(“y”)*2.54)))

Tuinkamer compleet v0.4.skp (1.5 MB)

No man its not.

Tuinkamer compleet v0.4 edit.skp (1.7 MB)

1 Like

Thanks! I will check what I have done wrong.

Ack! Capitalization matters! “y” is not “Y”?

1 Like

Doesn’t the ruby convert it into all lowercase anyways for processing? Example: you cannot have “BIG” and “big” as attributes. What does it effect if you do not respect the CAPS? Other than the obvious its just good practice to keep it consistent.

No, Ruby itself does not change capitalization (though I don’t know what the DC code itself might do - it is closed source). But in general, a string containing a lower case y is a different thing than one containing an upper case Y.

1 Like

The problem was with the third return value?

Does the if always need an else?

Yes it does.

I feel stupid,

Got the same error again.

If found out when editing attribute function the wrong quote sing is inserted.

=LARGEST(CURRENT(“LenY”)*2.54, 605, CURRENT("LenY”)*2.54)

You can see the last quote ” is wrong.

What can I do about this?

Turn off smart quotes on your Mac.


Thanks, that was my problem!

Ahh those dam smart quotes. :face_with_raised_eyebrow: They get everybody who DCs on a Mac at some point.

There is nothing smart about them. Apple has just let an half-obscure American typographical feature mess up the typing of a large part of the humanity. Europeans, for instance, have totally different rules about quote marks.

1 Like

Hahaha, dumb quotes.

« indeed we do » he said, rolling his french eyes up. :slight_smile:
also, in some countries, they still use the “anglo saxon” quote marks, but in some other places, they use a “different pair, not just straight ones”
Capture d’écran 2023-11-13 à 15.14.50

1 Like

Oh come on, this has little to do with Apple. Microsoft Word also supports smart quotes. The OP’s problem arose from using a word processor app to enter code instead of a code editor app.

It has to do with the conflict between English language keyboards (which have a single key for both opening and closing quotes) vs typesetting conventions that have long had distinct “curly quote” marks that differ between opening and closing, just as we have (),,{}, and Europeans have the double chevrons.

“Smart quotes” refers to data entry code that automatically converts straight quotes into curly quotes by detecting the start and end of a quoted block.

The conflict extends to computer character encoding, in which early systems such as ASCII didn’t have enough bits to encode both kinds, so they supported only the typewriter “straight” version. So, most programming languages don’t understand curly quotes. Correspondingly, code editing apps normally generate only straight quotes.

A problem still arises when text that originally contained only straight quotes is fed through a formatter that implements smart quotes - such as the markdown used by this forum. When posting code, unless you follow the correct process of setting it out with leading and trailing triple-backticks, the quotes will be smartened and cut-n-paste of a Ruby snippet will cause a syntax error.