Re: [Fxruby-users] timeouts...

[Hugh S. S. E. E. <hg...@dm...>]

On Tue, 29 Jul 2003, Lyle Johnson wrote:

> I'm not exactly sure what you mean. In the C++ library, there is an

Well, my discovering its existence was due to reading C++ docs....

> FXRuby, you create a timeout event by calling FXApp#addTimeout and, if
> necessary, destroy it by calling FXApp#removeTimeout.

...so that's fine. Thanks
>
> When you call FXApp#addTimeout to register a timeout event, it adds a
> new record to the application's internally-maintained list of timeout

So it is not tied into the individual object. OK.
        [...]
> those timeouts have expired. When a timeout comes due, the application
> sends a SEL_TIMEOUT message to the appropriate target (the one that you
> specificed when you added the timeout).

And when it came back from storage the event would have gone.  I
suspected that might be the case.
>
> None of the FXRuby objects are serializable via Marshal or YAML, so I'm
> not quite sure how to answer the last part of your question...

Fair enough, it won't be possible to do it that way.  I'll have to
write code for the (simpler) data I can marshal to do this.

        Thank you.
        Hugh