Unfortunately, the media elements don't expose volume control as an attribute, only as an object property, which we can't use here.

Webcam, cellphone, 3DS... whatever gives the best quality and is within reach. At this moment I have all three options, and I'd pick the phone.

Added beds for the villagers to use, but their placement is very badly done. I already have an idea on what better placement would be, which also works for other clutter, but haven't gotten to implement it yet.

The beds also have IDs matching their owners, so villagers can pathfind back to their beds when needed. Like say if I add the passage of time?

See, I could go into how actually using the actual native controls is the only way to get an actually native look and feel, but that's exactly what this is not supposed to be about. So thank you, Niko, for that.


Now, let's try to fix this. VB.Net had optional parameters (you all know what those are, right?) but C# didn't until version 4. According to the developers' blogs, this was because they needed time to properly define the behavior of that functionality, which sounds like a pretty good reason for delay to me. There are simple usage cases where the "correct" behavior is blatantly obvious, but then there's also complicated scenarios. And those are the cause of the delay.

Because on the CIL level, there's no such thing -- C# 4.0's optional parameters are filled in at compile time:

void MyFunction(int i, int j = 4) { ... }

MyFunction(2, 3);
MyFunction(2); //compiles as MyFunction(2, 4)

And that's why you can use the 4.0 compiler, set to target the 2.0 runtime, and still use things like var and optional parameters.

Ain't that a cool thing.

If there's one thing that's not so good about that pic, it's the pronounciation. Short O or long O? "Tron" is a short O, but "pony" is a long O. So what's "Trony"?

I just got Gaspar.

That's a thing you can get? Cool. I'll keep an eye out for that then.

It's actually a parasitic lifeform that got Samus' suit. Oh well.

Crime on the internet? Oh my. Why won't anybody think of the children?

Basically, they probably do. It's just, VB Classic already had it so they were pretty much forced to do it from day one.

It could've been a CIL-level function, but that would just open a whole 'nother can of worms.

Zombie Wario, ladies and germs.

Hey hey hey. It's "Kawa and I", for the record. If you remove me from your opening post, you get "me and Kawa had to". "Me had to". "Kawa and I had to".

The other is a matter of grammatical rules RRRRRUUURRRU.

OWEIOWEIOWEIOWEIOWEIOWEI!

I thought Rarity's whining worked okay.

That's just because sometimes they might try to overwrite shared system files. Nowadays, that's hardly an issue for the average app, but the installers themselves, being off-the-shelf, still have the warning.

And even then, in Win7, installers only need elevation because Program Files is protected. As long as they don't try to change things in the system directories, you don't need to close shit.

The same "they're off-the-shelf" origin can be blamed for the time estimate.

Considering the working directory is the first place LoadLibrary'll look when you don't specify a path (which is the preferred style anyway)...

Preinstalled with recent Windowses, loader'll guide you halfway through an upgrade if you need one... but it can still require DLLs, unfortunately.