Comments on: Immediate GUIs in XNA: Setup and a button

By: Haigha

Haigha — Fri, 02 Apr 2010 12:40:37 +0000

How you find ideas for articles, I am always lack of new ideas for articles. Some tips would be great

By: Roy Triesscheijn’s Weblog » Blog Archive » Immediate GUIs in XNA: Scrollbars

Tue, 30 Mar 2010 19:57:09 +0000

[...] Immediate GUIs in XNA: Setup and a button [...]

By: Roy Triesscheijn

Roy Triesscheijn — Fri, 19 Mar 2010 09:31:35 +0000

Damn, and I even did that two times. Altough it’s not really wrong, it’s of course nicer to say:
return mouse.LeftButton == ButtonState.Released && hotItem == id && activeItem == id;

And
return rectangle.Contains(new Point(mouse.X, mouse.Y)

The second one slipped in because at first I did some extra checks, but the first one is unexcusable, thanks for pointing these two out! I’ll fix them immediately.

By: Anonymous

Anonymous — Fri, 19 Mar 2010 08:15:52 +0000

Whats the difference:
if (mouse.LeftButton == ButtonState.Released && hotItem == id && activeItem == id) 40 return true; 41 return false;

or
return mouse.LeftButton == ButtonState.Released && hotItem == id && activeItem == id;

Basicly, what you are saying is:

if(something == true) return true; else if(something == false) return false;
That doesnt look right IMHO.

By: Roy Triesscheijn

Roy Triesscheijn — Fri, 19 Mar 2010 07:31:15 +0000

Why is that? If you only use a single statement after an if instead of something between { } that will get exectued. Or it will get skipped over if the if evaluates to false. Also returning true will immediately jump out of the method.

So its the same as:
if(something)
{
return true;
}
else
{
return false;
}

By: Anonymous

Anonymous — Thu, 18 Mar 2010 23:59:38 +0000

if(rectangle.Contains(new Point(mouse.X, mouse.Y))) return true; return false;

Code like this makes me giggle