----------------------
-- Mass compile and save with LV2019.

----------------------
-- Recompiled everything with LV2018

----------------------
-- From now on an error which occured while a msgs was created will not block the creation of other msgs still to come
-- Modified error dialog for the "Build Msg" function

----------------------
-- The GrayOut function had a small glitch which I corrected here. Note that "old" msgs (whose naming in the Do.vi is wrong) will not be shown in the main window if there name does not follow the MM naming conventions (But they will be shown in the error dialog before).

----------------------
-- Grayed out all entries in the tree whose names do not follow the MM naming conventions. These entries can not be overwritten

----------------------
-- Added the pssibility that the name of an already existing message does not follow the MM naming convention
-- Note that all msgs created by the MM will follow this rule. Therefore it not yet possible to overwrite a msg which does not do this
-- This version is not 100 % tested
-- All messages have to be either created new or a "tag" with the name "Method" has to be included in the xml file of the msg indicating the complete name of the corresponding method as a string, for example "CSPP_BaseActor.lvlib:CSPP_BaseActor.lvclass:After Launch Init.vi"

----------------------
-- It is now possible that more than one actor is located in the same library. It will always be checked which msg belongs to which actor during startup
-- Modified BuildDo again in order to get the ExpertMode working. This is still work in prpgress, since the result for an "Expert-Mode" Do.vi is ok but not perfect.

----------------------
-- Hopefuly corrected a small bug when calculating which ReceiverMsgs are shown in the ReturnMsg DialogBox depending on the Expert-Mode boolean.
-- Slightly modified the Help window.

----------------------
-- Used the TestMode to find countless bugs and corrected them. Therefore several changes had to be implemented, some examples are: For Return Messages there is now a "Send Return XXX.vi", only necessary accessor vis are created (because parent and child classes can not have the same vis...), and so on.
-- Already prepared VIs for Performance tests.
-- One remaining bug: Some messages will not work if the ExpertMode is off.

----------------------
-- The Test mode is now also working with Return Messages
-- Corrected a bug which occured when two classes with the same name but different libraries were present in the system (btw: LabVIEW crashes when a class tries to inherit from itself)

----------------------
-- Added a "Test"-Mode, reachable over Ctrl-F1. This mode needs the CSPP_MMTest package to be installed. Right now it does not work with return messages. (btw: Test was passed for all messages)

----------------------
-- Implemented the Expert-Mode for Return Msgs. Has to be tested a bit more.

----------------------
-- Corrected another bug in BuildDo.vi: In case of a return message the inputs of the receiver message were used to be connected to the Sender Action vi and not the outputs
-- Larger modifications to the ReturnMsgPanel: From now on he calculates which messages are possible with the sender methods connector pane. Everything else will not be shown to the user. In a next stel the expert mode has to be implemented.
-- Exchanged some deprecated VIs I used to check if a variant is an error cluster

----------------------
-- And another bug in the return msg corrected
-- Added Help file for Return Panel
-- Changed icon color of return msgs

----------------------
-- Revision of MessageMaker finished for the moment (still some bugfixing ongoing).

NOTE that all messages should be recreated!

----------------------
-- Added options for AsyncPV and AsyncDialogPV messages
-- Note that this is an internal test version and not fully tested!

----------------------
-- Mass compiled with LV2017

----------------------
-- Included a new checkbox to give the user the possbility to force the tool to overwrite thefront panel of the dialog.

----------------------
-- The GUI was completely renewed. Now it looks better, is more intuitive, easier to extend and more powerful if you want to create many messages at once. The can still be some logic errors in (these checkboxes...).

----------------------
-- The Acknowledge Message is now included and working (there is a small bug when switching frfom an Ack Msg to an Asynch Msg resulting in a warning => not so problematic)
-- Changed some symbols
-- Updated the Help window

----------------------
-- Added two new message types (Return + ReturnAndDialog)
-- ReturnMsg is partly implemented (only Do.vi and also this still has to be modified when CallerMsg has no parameters)
-- Fixed a bug in the Main.vi: When one switched between projects the actor list was not always proper updated
-- Slightly modified the helping txt files

----------------------
-- Mass compile with LV2016

--------------------
-- Added a symbol for unknown message types

--------------------
-- Updated MM to LabVIEW 2015 (not tested yet)
-- Slightly modified the Readme.txt

-- In the case of an PVUpdate Msg the MM will include a boolean called "Execute?" to the attribute data if the original Vi had no data inputs. In addition the Do.vi will be modified with an additional Case structure. (This procedure is tested)
-- The Tree in the GUI does not lose the last values once a message has been built
-- The Tree shows now the correct symbol when a PVUpdate Msg was built
-- The labels in the "Get Type.vi" of the actor control / indicator is now properly set

-- -- Change of Inheritance
-- -- More complex Build Do.vi
-- -- Included the GetType.vi
-- Not used files will now be deleted (Question remains if LabVIEW will rewrite them once the project is closed and saved)

Intermediate version: Try to make the program more robust so that it also reacts correct if there are already files in the msg folder.

BUT NOTE: This version here is not intended for usage!

-- The main Folder Name had to be changed again. For whatever reason LabVIEW expects that the folder starts with an "_".