Bug 1440 - frysk.event.EventLoop.start ()
Summary: frysk.event.EventLoop.start ()
Status: ASSIGNED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P1 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks: 1632
  Show dependency tree / graph
 
Reported: 2005-10-08 16:42 UTC by Andrew Cagney
Modified: 2008-01-09 13:27 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2005-10-08 16:42:41 UTC 
frysk.event.EventLoop has been modified so that it extends Thread, this makes
possible:

  eventLoop = new EventLoop ();
  eventLoop.start ();

(the async bugs are hopefully also fixed)
Comment 1 Andrew Cagney 2005-10-29 17:23:35 UTC 
begs the question, who should catch a failing event loop?

perhaphs the thing to do is extend EventLoop (possible?) with a wrapper that
starts the thread, but then catches any throw notifying the GUI which can then
decide if restarting the event loop is worthwhile.
Comment 2 Phil Muldoon 2006-07-19 16:17:03 UTC 
I tried this last night, and for some reason if I use the code as below I get no
updates from the Manager.host.requestRefreshXXX(). Using the old way
(Manager.eventloop.(...) and the updates come in fine.