Hard-coded marker number

[shae-wat]

The program is designed to handle 50 markers.

Over the summer I was able to get around this to handle c3d files with less than 50 markers. But to truly trust implementation and expand it to any marker number a refactoring is required.

The hard-coded marker number should be removed from the code by refactoring the areas that handle this hard-set number. First, hard-coded "50"s should be replaced with a variable. Then, hard-coded arrays (any other things affected by marker number) should have the way they interact with the code base abstracted such that any number of markers is ok. This may take awhile if done correctly. I will be referencing Martin Fowler's Refactoring: Improving the Design of Existing Code as a source of inspiration / design guidelines for my part in the refactoring process.

[lmjohns3]

Joseph added a compile-time constant defined in QtVR.pro as MARKER_COUNT (see https://github.com/EmbodiedCognition/QtVR/blob/master/QtVR.pro#L103).

It's not a runtime variable, but it does seem like this should help the code be able to handle other marker counts.

If nothing else it'll be easier to grep for MARKER_COUNT than for 50.