NetEXT - SFML.NET Extension Library based on Thor

[Laurent]

if (Math.Abs(mag) > Math.Abs(0) || (vec.X != 0 && vec.Y != 0))

What's the purpose of this double-check? How could X and Y be both non-zero if the length of the vector is zero? And do you really expect Math.Abs(0) to do something useful?

public static Vector2f normalizedVector2(Vector2f vec)
{
    float mag = VectorMagnitude(vec);
    return  mag != 0 ? vec / mag : vec;
}

I added assertions so now invalid vectors in debug configuration will throw an error

I think returning the zero vector in this case would be more natural than throwing an error. A vector with zero length is valid, it's just a special case to handle.

[zsbzsb]

I think returning the zero vector in this case would be more natural than throwing an error. A vector with zero length is valid, it's just a special case to handle.

Hmmm, I would like to know what Nexus thinks of this. I am open to change, but when I implemented the assertions I was following Thor's implementation. Personally I haven't done enough math dealing with vectors to know the best way to handle this.

[Nexus]

I think returning the zero vector in this case would be more natural than throwing an error. A vector with zero length is valid, it's just a special case to handle.

My point of view here is that UnitVector() claims to return a vector of unit length. If it doesn't, that's a violation of the method's postcondition. Analoguously, a vector of length zero is not a valid input -- you cannot compute the unit vector of a zero vector. Same thing if you compute the polar angle. In otherwords, the precondition is a non-zero vector argument, and Thor explicitly states that in the documentation.

I'm personally not a fan of hiding logic errors like this; if the user wants to handle zero vectors differently, he should do so explicitly. The nice side effect is that users who really want to compute a unit vector don't pay for a useless if statement.

[StormWingDelta]

if (Math.Abs(mag) > Math.Abs(0) || (vec.X != 0 && vec.Y != 0))

What's the purpose of this double-check? How could X and Y be both non-zero if the length of the vector is zero? And do you really expect Math.Abs(0) to do something useful?

lol Brain fart on my end.  For some reason went for double check when I didn't have to. XD

I think returning the zero vector in this case would be more natural than throwing an error. A vector with zero length is valid, it's just a special case to handle.

My point of view here is that UnitVector() claims to return a vector of unit length. If it doesn't, that's a violation of the method's postcondition. Analoguously, a vector of length zero is not a valid input -- you cannot compute the unit vector of a zero vector. Same thing if you compute the polar angle. In otherwords, the precondition is a non-zero vector argument, and Thor explicitly states that in the documentation.

I'm personally not a fan of hiding logic errors like this; if the user wants to handle zero vectors differently, he should do so explicitly. The nice side effect is that users who really want to compute a unit vector don't pay for a useless if statement.

Sometimes throwing an error is good other times like when doing AI calculations it can be annoying so I went for just returning the passed vector without doing anything to it since it won't crash me when I don't want it to. Although yes I'm not much of a fan of hiding errors like this either when they shouldn't be hidden.

[AbelToy]

If I use string as the Key for a TextureCache, it randomly gets freed? How can I use resources properly?

[zsbzsb]

If I use string as the Key for a TextureCache, it randomly gets freed?

What do you mean by randomly freed? If you think there is an issue I need a complete and minimal code example to test with.

How can I use resources properly?

There is an example in the source code for you to look at.

[eyeliner]

Hey there. Thank for this, but I can't build it.
It rants about this:

Error   1   The type or namespace name 'System' does not exist in the namespace 'SFML' (are you missing an assembly reference?)   D:\GameMaking\NetEXT\NetEXT\TimeFunctions\Stopwatch.cs   2   12   NetEXT

With loads of errors like this.

And these warnings:

Warning   49   'NetEXT.Particles.ParticleSystem.ExpiringTime' overrides Object.Equals(object o) but does not override Object.GetHashCode()   D:\GameMaking\NetEXT\NetEXT\Particles\ParticleSystem.cs   281   23   NetEXT
Warning   55   'NetEXT.Particles.ParticleSystem.TimeLink<TimeType,ValueType>' overrides Object.Equals(object o) but does not override Object.GetHashCode()   D:\GameMaking\NetEXT\NetEXT\Particles\ParticleSystem.cs   328   23   NetEXT

I want to build a 64bit version, because I downloaded the .dll present and apparently it is not 64bit.

Am I being dense, or some compatibility somewhere lurks in my vicinity?

[zsbzsb]

NetEXT has been updated to work with the latest SFML.NET version (the soon to be released 2.2 version). So you will need to download and compile the latest SFML.NET and grab the latest nightly builds of CSFML from here (or compile it yourself). As for the warnings, you can safely ignore them.

[StormWingDelta]

Hello, was just wondering if this even needed to be updated from the 2.2 release?

[DurtyFree]

Is this library still in active development?