Doesnt seem so unfortunately. The only difference is several if/then/elses leading to different menus about every product.
I even assigned NULL_OBJECT to CJ Object calling Collectforced() afterwards - and prior to QUIT. The result was the same ; 2-3 annoying seconds not trapable by the debugger as the are after the final QUIT...
as a long time user of the CodeJock OCX controls,I remember that there is a weird thing with timers. As far as I remember the Ribbon fires a timer event and this gave us all kind of trouble. So we added this to the dispatch method of the window which owns the OCX :
if oEvent:Message == WM_TIMER
if oEvent:wParam =6828
KillTimer( self:Handle() , oEvent:wParam )
Case closed - and thanks all for the contribution...
All tries to Quit() decently failed.
The real problem was the instantiation of a TWAIN OCX Global Object (scanner) that existed in the Start() method of the app. This in some way interfered with CJ Objects and the result was this really annoying hang when closing the app.
Obviously the auto call of GC when exiting lead to the problem.