On Thu, Feb 4, 2010 at 1:47 AM, Rick McGuire <object.r...@gmail.com> wrote: > On Wed, Feb 3, 2010 at 11:32 PM, Mark Miesfeld <miesf...@gmail.com> wrote:
>> What I was thinking was: for the C++ API, add an API for AttachThread >> that took a parameter which marked the activity for that thread to >> avoid PeekMessage. Them from ActivityManager::addWaitingActivity this >> flag would get passed down to waitKernel() and ultimately >> waitHandle(). > > I'm not really in favor of exposing this bit of Windows-specific > problem in the portable APIs. Maybe the solution is to make the > RexxSetMessageLoop() API functional again, but have it work on a > per-thread basis rather than globally the way it used to. Yeah, I didn't like it too much either. Using thread local storage, the whole thing could be implemented in the Windows specific files, except for how to set the flag on. (If you think of on as being don't use PeekMessage.) Using RexxSetMessageLoop would solve that last part. -- Mark Miesfeld ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
