I just want to be really really sure

[Richard C Bishop]

So....what exactly is wrong with that?

[Lost User]

Did you check that the Text property Getter didn't make changes to the underlying data and so make that a valid statement. e.g.

private string _text;
public string Text
{
Get{
if (_text == null)
{
_text = "Empty";
return _text;
}
if (_text == "Empty")
_text = "";

return _text;

}
}

MVVM # - I did it My Way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')

[Argonia]

_Maxxx_ wrote:

if (_text = "Empty") _text = "";

This will be always be true no matter what _text is :D except for F# but there the if else operation contains then :)

Microsoft ... the only place where VARIANT_TRUE != true

[Lost User]

Thanks for the human compiler - I've fixed it.

MVVM # - I did it My Way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')

[Lost User]

AnalogNerd wrote:

if ((tbRoute.Text != "") && (tbRoute.Text != "") && (tbRoute.Text != "")) {

Third time is the charm

[Gary R Wheeler]

I've unintentionally had that happen after some refactoring. A couple text boxes contained values, and were later converted to a single box. Refactoring the name of the second to be the same as the first created the circumstance found here. Of course, that situation only lasted for a little while, since I did check all the references to make sure nothing too stupid happened...

Software Zen: delete this;

[Robert Rohde]

No it won't. It wouldn't compile...

[Argonia]

It depends on the compiler and the language you are writing in. In c++ it will compile and run and you will be looking for a bug :D

Microsoft ... the only place where VARIANT_TRUE != true

[MacSpudster]

At least give the guy credit for ensuring that no variable leaves empty-handed.

[ian dennis 0]

Somebody knows the "Tell me 3 times and it must be true" rule (see Heinlein's "Number of the Beast")