From: Fredrik Jagenheim <jagenheim@...>
Date: 2005-09-29T16:26:58+09:00
Subject: Re: Even more WIN32OLE_EVENT

------=_Part_1430_27123757.1127978815532
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 9/29/05, Daniel Amelang <daniel.amelang@gmail.com> wrote:
>
> When I've used PeekMessage/GetMessage like functions, I've called them
> via ruby-dl instead of win32ole. Have you tried that route?


It's not the actual PeekMessage/GetMessage functionality I want. I want the
functionality I get from win32ole. But since win32ole_event#message_loop is
implemented using PeekMessage, it will use 100% CPU while running.
Recompiling win32ole using GetMessage was a hack that didn't work as well a=
s
I had hoped...

Perhaps the only solution is to rewrite the interaction with my OLE object
using a custom C-library that I can call from ruby and just ditch the entir=
e
win32ole lib idea.

--F

------=_Part_1430_27123757.1127978815532--