THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 17/02/2006 at 09:55, xxxxxxxx wrote:
GeDialog::Message() only receives messages specificly for the dialog. GeDialog::CoreMessage() will receive more generic messages from Cinema 4D. Best to check which messages are sent, but EVMSG_CHANGE might be worth checking for. Whenever I need to know if some sort of message is being received in a particular situation, I use GePrint() from the either of these methods to see what it might be.
Or, you may need to set up a timer and check the available document(s) periodically. I normally don't tie my dialogs to documents and objects except through user-interaction.
Causes for Cinema 4D startup plugin crashes are diabolically difficult to track down. As you note, you really can't debug, not even to the Console Window or a command line. The best course of action in such situations is to go to the top levels of your plugin code, comment out as much as possible, and add lines or sections back in one at a time while compiling and testing.
Not much for Maxon to do about this. Since plugins are static libraries, they have no control over the execution of the code other than executing it.