RELEASE WARNINGS!
* Due to the current XCM design, when a program has a LIB attached,
XCM might get two messages from the program. One that the program
does natively and the other one from the attached library. XCM
detects when a program sends the LIB message, and then starts
to ignore the NON-LIB message because it is redundant.
When an XCM library was attached, XCM received a LIB message,
and thus flagged the object as having a lib attached, and
ignored the NON-LIB message.
When the library was detached, the library is no longer sending
the library message for the program, but the non-lib message is
still being ignored.
The issue will be corrected in the future release. The workaround
solution is to bounce XCM when one LIB is removed and a different
LIB is attached, or no lib is attached.
If this article did not provide a solution, please open a case with our support team by sending an email message to support@xypro.com.