Jump to content

  • Log In with Google      Sign In   
  • Create Account

We're offering banner ads on our site from just $5!

1. Details HERE. 2. GDNet+ Subscriptions HERE. 3. Ad upload HERE.


Member Since 31 Jan 2003
Offline Last Active Oct 06 2014 11:45 PM

Posts I've Made

In Topic: So...the world has ended. What do you do now?

19 February 2012 - 06:40 PM

Well that's easy. Learn the secret art of Hokuto no Ken and declare myself as Raoh the Conqueror.

Can there be any other options???

Lol, nice reference and an excellent choice. I haven't seen Fist of the North Star in quite a while, but how are you going to fare against a gun or a car? *thump thump*

In Topic: Right Way To Read File From x360?

15 May 2011 - 08:18 PM

A quick Google returned http://msdn.microsoft.com/en-us/library/bb199094.aspx

In Topic: Problems with my 2D animation

09 March 2011 - 07:05 PM

The only thing that catches my eye is:
int width = Texture.Width / Rows;
int height = Texture.Height / Columns;

The 'Rows' and 'Columns' need to be swapped.

In Topic: Is this a valid warning?

15 February 2011 - 11:33 AM

I have registered a value type (not a handle) like this one:

class Message
    Message(const string& in type);
    Message& set(const string& in val);
    // (more stuff)

I usually use it like this:

Mgr.post( Message("whatever").set("foo").set("bar") );

The thing is that although it works correctly, I keep getting this warning during compilation:

tutorial_trigger.as (19, 35) : A non-const method is called on temporary object. Changes to the object may be lost.

Is this warning a valid one?
I 'm asking because it adds "noise" to the output which may make me miss other important (and valid) warnings/errors...

Without actually knowing your implementation, I can't really say. However, if I had to guess, I'd say that your set method returns "this". If so, you could ignore the warning in your case.

The reason you're getting the warning is because, from the compiler's point of view you're returning a variable and calling two methods that modify said variable (non-const method), but you don't store it anywhere (temporary object.)


In Topic: Small detailed world vs Large undetailed world

31 January 2011 - 10:56 PM

I apologize, I guess I'm just not understanding. From what you just said, it seems like it would be a large, detailed world not a small, detailed world. Maybe you could give an example of each?