Make userMessage and userErrorMessage consistent.

LogUtil.userErrorMessage changes the contents of its dialog depending
upon the content (and/or length) of the incoming message, and this
behavior seems to work pretty well.

Prior to this commit, LogUtil.userMessage would simply wrap the
incoming message in a JLabel and display it, making long messages
nearly unreadable. This commit just copies userErrorMessage and
displays the results from LogUtil.getMessageComponent.

I also went ahead and took advantage of generics and StringBuilder
within LogUtil.getMessageComponent.
Fix problem with leaving full screen mode.

All this commit does is explicitly run the logic of “resetFullScreen”
on the EDT via invokeLater.

I did test things with GuiUtils.invokeInSwingThread and it seemed to
work, but I opted for invokeLater because:

1. GuiUtils.invokeInSwingThread seems semantically equivalent to always
using SwingUtilities.invokeAndWait (and that shouldn’t be called from
the EDT).

2. Adding the runnable to the end of the EDTs queue—rather than
executing the runnable immediately—seems like the safer choice, as
there could be situations where events/threads reference the
fullScreenWindow JFrame that has already been disposed and nulled out.
Merge pull request #87 from jon4than/resetfullscreen-invokelater

Fix problem with leaving full screen mode.
Merge pull request #86 from jon4than/logutil-consistency

Make userMessage and userErrorMessage consistent.
image capture for the crosssection often ends up black,  so, I added the crosssection view manager to the list, and added a few wait cursors for loading data, and wait for 1 second before capture image for all crosssection. The local test is good so far, but I was hoping for better solution.
Merge remote-tracking branch 'origin/master'
fixed NPE reported by JeffM