Multiple Conditionals on if statement?

[JackieBlue1970]

Is it possible to have multiple conditions on an if statement? Such as

If x=3 and y=5 then...

I’ve tried a couple of ways and it doesn’t appear to work. Thanks

[FourthWorld]

It is. What do you have that isn't working?

[JackieBlue1970]

It is. What do you have that isn't working?

Thanks for your response. Don’t have the code here but I was checking if two fields were empty. Something like:

If field1 is empty and field2 is empty then...

[FourthWorld]

You've got the concept down, I'll bet the answer is in some nuance of the syntax used.

[bogs]

I agree with Richard, I used the syntax you provided for this demo and it works as expected.

The setup is simply 3 fields and 2 buttons -

Would you like anchovies with that?

aPic_And_Or.png (6.13 KiB) Viewed 6825 times

The code in the "And" button -

Code: Select all

on mouseUp
   if (field 1 is empty) and (field 2 is empty) then
      put "True" into field 3
   else
      put "False" into field 3
   end if
end mouseUp

The code in the "Or" button -

Code: Select all

on mouseUp
   if (field 1 is empty) or (field 2 is empty) then
      put "True" into field 3
   else
      put "False" into field 3
   end if
end mouseUp

It works as expected, with or without the '()' surrounding the values, see attached demo stack.

andorlogic.livecode.zip

(844 Bytes) Downloaded 167 times

[dunbarx]

What everyone said. There is no limit to the number of snippets within such a construction.

But beware how you form mixed "and" and "or" constructions. This has nothing to do particularly with LC, but you must enclose the "or" parts in a mixed statement:

Code: Select all

if (a = 3 or b = 4) and c = 5 and d = 6 and (e = 7 or f = 8) then...

You may not get an error if this sort of thing is not built correctly, but you will not get the results you expected.

Craig

[jacque]

Also, a field with a single carriage return {or more) may look empty but it's not. If you aren't getting a syntax error but the result is not what you expect, that may be the reason.

To get around this I sometimes check for the number of words in the field instead of empty.

Code: Select all

if {the number of words in fld 1 is 0} and {the number of words in fld 2 is 0} then... 

[JackieBlue1970]

Thanks guy (and gals). Pretty sure it was something else.

[dunbarx]

What Jacque said.

a field with a single carriage return {or more) may look empty but it's not

I have been burned by this so often in the past that I always make sure it does not happen. Lots of ways to, say, disable the return key, or insert a little massaging of input data to preclude an empty first line.

Craig

[JackieBlue1970]

I figured out the issue. I was using

If field "Fld1" is empty and field "Fld2" is empty then

instead of if "Fld1" is empty...

Field appears to be a key word of some sort. Not throwing an error but wouldn't work properly.

[bogs]

If field "Fld1" is empty and field "Fld2" is empty then

instead of if "Fld1" is empty...

I don't think that is the issue, JackieBlue1970

Field is indeed a keyword, it identifies the object you are testing, in this case field "fld1" and field "fld2". I modified the stack I posted above to include the wording because that is exactly how you should be referring to controls/objects, and it works here after I named my fields "fld1" and "fld2".

If it wouldn't be asking too much, could you possibly post the code you had before the changes you made? I, and I'm sure many others, would love to take a look at what was going on that was causing the original problem.

Put me in coach, I'm ready to play...today...

[dunbarx]

Hi.

No.

The correct syntax would be:

Code: Select all

 if fld "Field 1" is empty

You have to have a control reference, apart from however you, er, reference that control.

What you describe would throw an error.

Craig

[bogs]

What you describe would throw an error.

Not necessarily so much, although it should. Jacque and I had a long bit of a thread about just such matters when I first got here, because I couldn't understand how I could reference a control either with the name in quotes or not.

Code: Select all

button cmdQuotes

would work, and I asked is quoting the name a requirement or just a suggestion, because I found that to be confusing.

Of course, that may have been corrected to be enforced now, but Jacque did say it was recommended to always quote the name going forward, and I agree that it is the safest course.

[Klaus]

If you don't put the name in quotes, then the engine searches the whole RAM
(script, local and global vars) for a variable with that name.

This means:
1. it will takes more time, OK, a tiny bit maybe, but you get the picture.
2. If you really have a variable with that name somewhere, you are licked!
3. this will not work with names consisting of two or more words.

[bogs]

All of which are very good reasons to always quote the name, now we need to find out what is happening in poor JackieBlue1970's case