how to IF?!

[Lost User]

Ok so more like this: if (BP_S.Text.Length == 0 || BP_D.Text.Length != 0)?

[Migounette]

I prefer this for String type: bool isBad = ((String.IsNullOrEmpty(text1) == true) || (String.IsNullOrEmpty(text2))) My 2 cents

[Jassim Rahma]

yes but this code will force the user to enter one of the textbox.. What if the user wants to leave the null?

[Lost User]

Ok it's quite late here and I'm tired so I could be wrong, but I'm fairly certain that if they are both null, that condition will evaluate to true

[Jassim Rahma]

it's ok.. rest now :) I will also sleep and come back later... it's 1:30am here in Bahrain.. Sweet Dreamz :)

[AspDotNetDev]

Wow, this is probably the first time I've seen a valid use for the EXCLUSIVE OR operator:

if (!(string.IsNullOrEmpty(textBox1.Text) ^ string.IsNullOrEmpty(textBox2.Text)))
{
MessageBox.Show("Valid");
}
else
{
MessageBox.Show("Invalid");
}

You could also do that with && and ||, but this is probably the most succint technique.

[Forum Guidelines]

[Lost User]

aspdotnetdev wrote:

but this is probably the most succint technique

Maybe 2 or 3 characters shorter :)

[Luc Pattyn]

most succinct? if exclusive OR is what the OP wants, then there is no need for XOR, OR, AND operators! Mind you, TextBox.Text never returns null.

MessageBox.Show((textBox1.Text.Length==0)==(textBox2.Text.Length==0)?"Valid":"Invalid");

:)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]

---

Getting an article published on CodeProject should be easier and faster for Bronze and Silver authors.

---

[NavnathKale]

:doh:

if((!String.IsNullOrEmpty(BP_S.Text) && !String.IsNullOrEmpty(BP_D.Text)) || (String.IsNullOrEmpty(BP_S.Text) && String.IsNullOrEmpty(BP_D.Text)))

Mark as answer if its really satisfies ur query !!!! :)

modified on Saturday, April 10, 2010 8:52 AM

[Lost User]

Now that's interesting, because that wouldn't allow you to fill in the second textbox if you didn't fill in the first as well - and he never said anything about that. Basically it's the same as aspdotnetdev's, but in the least-succinct way.

[AspDotNetDev]

You fool! It can be MUCH more succint!

MessageBox.Show((textBox1.Text.Length>0)==(textBox2.Text.Length>0)?"Valid":"Invalid");

[Forum Guidelines]

[Luc Pattyn]

Do you mean

MessageBox.Show(((tb1.Text.Length>0)==(tb2.Text.Length>0)?"V":"Inv")+"alid");

? :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]

---

Getting an article published on CodeProject should be easier and faster for Bronze and Silver authors.

---

[AspDotNetDev]

Haha, I did exactly that, but then found it to take up more characters than the other method, to be less clear, and to potentially take up more processing time (the strig concatenation). If you make both words lowercase, you can get it down to exactly the same number of characters as the one I posted, but it still has the other issues. But nice try. ;)

[Forum Guidelines]

[Luc Pattyn]

correct.

MessageBox.Show((tb1.Text.Length>0)==(tb2.Text.Length>0)?"OK":"!OK");

:)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]

---

Getting an article published on CodeProject should be easier and faster for Bronze and Silver authors.

---

[AspDotNetDev]

I had a nice long reply I was working on, but my Internet decided to go down just as I posted it. So, lucky for you, you get the short version instead:

((a.L>0)==(b.L>0)).S();

;P

[Forum Guidelines]

[AspDotNetDev]

harold aptroot wrote:

he never said anything about that

FYI, my impression is that the OP wants either both to be filled in or neither to be filled in. Filling in one without filling in the other is not allowed.

[Forum Guidelines]

[Luc Pattyn]

why would you need a long reply to come up with a succinct code snippet? Anyway, with a real pre-processor, it is trivial:

T

:)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]

---

Getting an article published on CodeProject should be easier and faster for Bronze and Silver authors.

---

[Lost User]

Ok, I think he just said that he wants a truth table like this:

D S result
0 0 1
0 1 1
1 0 0
1 1 1

IOW "everything is OK except skipping the second textbox after filling in the first" The smallest formula for that truth table is, AFAIK, (¬D)v S (where v is OR) Or maybe I'm just taking his explanation too literally..

[AspDotNetDev]

If my Internet didn't go down, you'd know. ;P Why use a letter with such a high ASCII value? This seems more optimal:

A

As a bonus, your left pinky is already on that letter. :rolleyes:

[Forum Guidelines]

[AspDotNetDev]

The OP said "one textbox is not null then the other should not be null as well". Order of the textboxes is never stated or implied. So "0 1" and "1 0" should have the same result ("0").

[Forum Guidelines]