Jump to content

  • Log In with Google      Sign In   
  • Create Account

Banner advertising on our site currently available from just $5!

1. Learn about the promo. 2. Sign up for GDNet+. 3. Set up your advert!


Member Since 08 Aug 2000
Offline Last Active Today, 02:22 PM

Posts I've Made

In Topic: Another basic array C problem

19 May 2015 - 11:34 AM

If you are not writing something that needs to be cross-platform there is no reason whatsoever to not use Visual Studio Community edition. I don't know what wintertime is concerned about above: a "Microsoft account" is just a banal free account that you might even already have if say, you, ever set up an outlook.com or hotmail email address. Anyway it takes about a minute to create an account and is free.

I would not agree with that. I'm using MSVC at work and I'm now using QtCreator with MinGW at home for my hobby. The only thing I miss at home are the debugging tools MSVC has (although QtCreator certainly has become more comfortable since I have started using it). For everything else I need QtCreator (and the compiler with extremely decent C++11/C++14 support) is doing an equivalent or better job.
That said, for someone new to C++ I would still recommend to start out with some kind of reasonable MSVC. It's simpler to find help on the weband especially precompiled libraries.

If you do care about being cross-platform there is still no reason to use Dev-C++ which hasn't been updated in a decade at this point.

While I can agree on the verdict (avoid Dev-C++ at all cost), the statement as given is not completely correct. Bloodshed Dev-C++ has not been updated in more than a decade, but there are two or three much newer forks around (although I think one of them is a bit abandoned again). However, I still would not advise anyone to use any Dev-C++ at this point. Code::Blocks and QtCreator are decent alternatives to MSVC (still not what I would suggest to a newbie, though, as said above).

In Topic: Triangulation

19 May 2015 - 11:09 AM

From reviewing the links, I get the impression that neither of you actually read the third and fourth paragraph of my previous post.  My question was not how to divide the polygon into triangles, but how to do it in such a way that I don't have to keep doing it over again every time a point moves.

I don't see how you reach that conclusion. You have a problem which is neatly divided into two components: triangulating an arbitrary polygon and and re-triangulating as a response to moving points. I can help with the triangulating part since I looked for something similar a while back (hence the links).
The other component of the problem does not really interest me but it's clear solving the first component is already helpful. At worst you could just triangulate the polygon every frame. Depending on what exactly you want to do that might end up being very sufficient. A good solution would still be to trigger a new triangulation when you detect you need to (Spiro probably gave the right suggestion there). A perfect solution would be to use the already existing triangulation and only modify those bits which need to change. Personally I doubt there is something like that prepared, at least in the free and non-GPL part of the available sources (since those were my constraints when I looked for it).

In Topic: Triangulation

19 May 2015 - 08:31 AM

A combination of this and this should probably get the job done.

In Topic: Another basic array C problem

17 May 2015 - 06:18 AM

In all honesty who doesn't have an MSN account these days, as they are used for Skype, xbox live, MSDN, office 365, windows phone, and just about everything ms offer...

I'm not using any of that outside work and I would not use work accounts for private endeavors.

In Topic: livecoding.tv

14 May 2015 - 02:05 AM

Just letting fellow programmers know about a site to for just coding

Well, the first time I encountered that site was when an freshly created account tried to drop that link in several places right here using the typical spammer behavior. Anyone using these practices will be more trouble than they are worth in the long run so I would discourage anyone from using that place.