I ran across this problem and note it was discussed back in 2007 (see part of the thread below). I could not find any reference to this in the j602 documentation, so I was wondering what the latest thinking is with regard to getting around this issue?
Ed Cox Principal Data Analyst ed....@carefusion.com<mailto:ed....@carefusion.com> MedMined(tm) ---------------------------------------------------------------------------------------------------- bill lam bbill.lam at gmail.com <mailto:programming%40jsoftware.com?Subject=%5BJprogramming%5D%20OLE%20Server%20Busy%20dialog%20box&In-Reply-To=F4E8E6AECDF8432F9180149E07ACEF6C%40EricPC> Thu Dec 13 22:35:15 HKT 2007 * Previous message: [Jprogramming] OLE Server Busy dialog box <http://www.jsoftware.com/pipermail/programming/2007-December/009066.html> * Next message: [Jprogramming] forward differences <http://www.jsoftware.com/pipermail/programming/2007-December/009073.html> * Messages sorted by: [ date ]<http://www.jsoftware.com/pipermail/programming/2007-December/date.html#9067> [ thread ]<http://www.jsoftware.com/pipermail/programming/2007-December/thread.html#9067> [ subject ]<http://www.jsoftware.com/pipermail/programming/2007-December/subject.html#9067> [ author ]<http://www.jsoftware.com/pipermail/programming/2007-December/author.html#9067> ________________________________ 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 _________________________________________________ This message is for the designated recipient only and may contain privileged, proprietary or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. Dansk - Deutsch - Espanol - Francais - Italiano - Japanese - Nederlands - Norsk - Portuguese Svenska: www.carefusion.com/legal/email ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
