#1 Player Implementation Problem in LogToScenes

[Matt]

Bug: Player Implementation Problem in LogToScenes.class

Abstract: For the purposes of converting Logs to
Scenes, the LogToScenes application formerly
catagorized players generically (disregarding
teammate/opposing team). A recent implementation
involves a proper catagorization, by filling 3
seperate lists (teammates, opposing, unknown) rather
thatn one.

Description: After implementing the usage of
teammates/opponents/unknowns ArrayLists rather than
simply logging players to an arraylist, the method
parseSeeInfo(...) in LogToScenes.java still calls
placeObjects(logSee.getPlayerList(), ...). However,
m_player_list is no longer being filled by the
VisualInfo.java : parse() method. Instead, three other
catagorized arraylists are filled.

Symptoms:
When a scene is generated, ALL visable players will
appear in the bottom-left of the visual table (left
column/bottom row) regardless of their actual position.

Solution:
LogToScenes.java : parseSeeInfo(...) should contain:
placeObjects(logSee.getUnknownPlayersList(),
numRows, numCols);
placeObjects(logSee.getTeammatesList(), numRows,
numCols);
placeObjects(logSee.getOpponentsList(), numRows,
numCols);

!NOT:
placeObjects(logSee.getPlayerList(), numRows,
numCols);

Conclusion:
Upon upgrading the current implementation, this was
accidentally omitted. The errors that resulted from
this caused Over-Generalization in scene selection.