AcRx messages

[Anonymous]

Hi group, I noticed, after being driven crazy for a day by unexplained crashes, that during app unloading, acad2000 sends a kUnloadDwgMsg before the expected kUnloadAppMsg. Anyone knows the reason? More generally, is there a documentation source for message sequences? TIA alex

[Anonymous]

> sends a kUnloadDwgMsg before the expected kUnloadAppMsg. > Anyone knows the reason? That's the logical order of a normal application life cycle: kInitApp, kLoadDwg for all open drawings, then kUnloadDwg for all open drawings, then the very last thing your app does is kUnloadApp. This is documented in the ObjectARX SDK (under "Sequence of Events in an ObjectARX Application"). :) -- Owen Wengerd President, ManuSoft ==> http://www.manusoft.com VP Americas, CADLock, Inc. ==> http://www.cadlock.com

[Anonymous]

Thank you, Owen. I must've missed it. Are there more sources for message sequences? I experimented with dwg window subclassing and catching the VK_RETURN. Sometimes I get 2 messages for one keypress (naturally - KEYUP and KEYDOWN), most of the time one message. In some cases (as when terminating user string input during a TEXT command), I get no message at all. I'll appreciate any pointers. alex "Owen Wengerd" wrote in message news:4116469d$1_2@newsprd01... > That's the logical order of a normal application life cycle: kInitApp, > kLoadDwg for all open drawings, then kUnloadDwg for all open drawings, then > the very last thing your app does is kUnloadApp. This is documented in the > ObjectARX SDK (under "Sequence of Events in an ObjectARX Application"). 🙂