Eric Iverson wrote:
What would you suggest? I'd be willing to switch things around. That is,
have the J startup Ole initialize be for no timeout and then users could
use your workaround if they wanted one. In either case this will be
documented in the User Manual Ole pages.
Another approach if J is a MFC application calling AfxOleInit() to initialize
COM, then it could provide hook to call
AfxOleGetMessageFilter()->SetMessagePendingDelay(nTimeout);
AfxOleGetMessageFilter()->EnableBusyDialog(FALSE);
eg. add new wd commands like
wd 'oledSetMessagePendingDelay 60000' NB. 60 second, 0 means wait indefinitely
wd 'oleEnableBusyDialog 0' NB. enable/disable dialog
I just notice a side effect of my workaround is that the screen does not repaint
itself during calling ole methods and it needs wd'msgs' to repaint.
--
regards,
bill
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
