Automatic generation produced by ISE Eiffel
class EV_APPLICATION_HANDLER General cluster: interface description: "Before SCOOP appeared, the event loop of a graphical application would run in the main thread after creating the initial graphical objects. That thread would enter an event loop to process new events. That thread was also called the GUI thread. In SCOOP mode this doesn't work because a processor stuck in a loop cannot process any logged calls. In other words, it means that you cannot perform calls on a separate widget my_widget as they will be logged but only applied after the processor has completed its event loop and exited its current application of a call. To circumvent this, we require the following guidelines. A GUI processor is created, this is where the EV_APPLICATION object and all GUI objects are created. The GUI processor is similar to the GUI thread in non-SCOOP mode. However we require the GUI processor to not do anything else after calling {EV_APPLICATION}.launch so that it enters the idle mode of SCOOP processors. Internally when calling launch from the EV_APPLICATION instance, we will create a separate instance of EV_APPLICATION_HANDLER which will continuously log calls to process events on the GUI processor. Since the GUI processor is idle, it will be able to log and apply calls coming from any other separate processors that wants to interact with the GUI." create: make Ancestors EV_ANY_HANDLER -- Generated by Eiffel Studio --
For more details: eiffel.org