\ j/:ddlZddlZddlZddlZddlmZddlmZddlmZddlmZe edoej Z GddZ Gd d ej Zed ed ed dS)N)app)clock)event)compat_platformis_pyglet_doc_runcJeZdZdZdZdZdZdZdZdZ d d Z d Z d Z dS) PlatformEventLoopzX Abstract class, implementation depends on platform. .. versionadded:: 1.2 cftj|_tj|_dSN)queueQueue _event_queue threadingEvent _is_runningselfs I/DATA/AppData/hermes/venv/lib/python3.11/site-packages/pyglet/app/base.py__init__zPlatformEventLoop.__init__7s&!KMM$?,,c4|jS)zReturn True if the event loop is currently processing, or False if it is blocked or not activated. :rtype: bool )ris_setrs r is_runningzPlatformEventLoop.is_running;s &&(((rch|j|||f|dS)aPost an event into the main application thread. The event is queued internally until the :py:meth:`run` method's thread is able to dispatch the event. This method can be safely called from any thread. If the method is called from the :py:meth:`run` method's thread (for example, from within an event handler), the event may be dispatched within the same runloop iteration or the next one; the choice is nondeterministic. :Parameters: `dispatcher` : EventDispatcher Dispatcher to process the event. `event` : str Event name. `args` : sequence Arguments to pass to the event handlers. N)rputnotify)r dispatcherrargss r post_eventzPlatformEventLoop.post_eventCs3* z5$7888 rc |jd\}}}|j|g|Rn!#tj$rYdSt $rYnwxYwP)zzImmediately dispatch all pending events. Normally this is called automatically by the runloop iteration. TFN)rgetdispatch_eventr EmptyReferenceError)rrevntrs rdispatch_posted_eventsz(PlatformEventLoop.dispatch_posted_events[s   )-):)>)>u)E)E& D$) )$666666;   !      s,0A A Ac td)aNotify the event loop that something needs processing. If the event loop is blocked, it will unblock and perform an iteration immediately. If the event loop is running, another iteration is scheduled for immediate execution afterwards. abstractNotImplementedErrorrs rrzPlatformEventLoop.notifyjs"*---rcdSr rs rstartzPlatformEventLoop.starts rNc tdNr(r)rtimeouts rstepzPlatformEventLoop.stepv!*---rc tdr0r))rfuncintervals r set_timerzPlatformEventLoop.set_timeryr4rcdSr r,rs rstopzPlatformEventLoop.stop|r.rr ) __name__ __module__ __qualname____doc__rrrr&rr-r3r8r:r,rrr r 1s ---)))0   ...   .......     rr ceZdZdZdZdZdZdZdZdZ dZ d Z d Z e d Zejd Zd ZdZdZer dZdZdZdSdS) EventLoopaThe main run loop of the application. Calling `run` begins the application event loop, which processes operating system events, calls :py:func:`pyglet.clock.tick` to call scheduled functions and calls :py:meth:`pyglet.window.Window.on_draw` and :py:meth:`pyglet.window.Window.flip` to update window contents. Applications can subclass :py:class:`EventLoop` and override certain methods to integrate another framework's run loop, or to customise processing in some other way. You should not in general override :py:meth:`run`, as this method contains platform-specific code that ensures the application remains responsive to the user while keeping CPU usage to a minimum. NFcttj|_tj|_d|_dS)NF)r Condition_has_exit_conditionr get_defaultrrs rrzEventLoop.__init__s.#,#6#8#8 &(( rcd|_|tj}||dd|_|js0|}|||j0d|_|d| dS)aBegin processing events, scheduled functions and window updates. This method returns when :py:attr:`has_exit` is set to True. Developers are discouraged from overriding this method, as the implementation is platform-specific. Fon_enterTon_exitN) has_exit _legacy_setuprplatform_event_loopr-r"ridler3r:)rrJr2s rrunz EventLoop.runs  !5!!### J'''- .iikkG  $ $W - - -- .  I&&&  """""rcddlm}d|_tjD]*}||+dS)Nr)WindowF) pyglet.windowrN_enable_event_queuerwindows switch_todispatch_pending_events)rrNwindows rrIzEventLoop._legacy_setups`((((((%*"k - -F        * * , , , , - -rcx|}tj|j|dS)a$Called by pyglet internal processes when the operating system is about to block due to a user interaction. For example, this is common when the user begins resizing or moving a window. This method provides the event loop with an opportunity to set up an OS timer on the platform event loop, which will continue to be invoked during the blocking operation. The default implementation ensures that :py:meth:`idle` continues to be called as documented. .. versionadded:: 1.2 NrKrrJr8_blocking_timerr1s renter_blockingzEventLoop.enter_blockings3))++ ))$*>HHHHHrcFtjdddS)z{Called by pyglet internal processes when the blocking operation completes. See :py:meth:`enter_blocking`. N)rrJr8rs r exit_blockingzEventLoop.exit_blockings# ))$55555rcx|}tj|j|dSr rVr1s rrWzEventLoop._blocking_timers1))++ ))$*>HHHHHrcb|j}|j|}tjD]V}|s|jrK|jrD||d| d|_W|j dS)akCalled during each iteration of the event loop. The method is called immediately after any window events (i.e., after any user input). The method can return a duration after which the idle method will be called again. The method may be called earlier if the user creates more input events. The method can return `None` to only wait for user events. For example, return ``1.0`` to have the idle method called every second, or immediately after any user events. The default implementation dispatches the :py:meth:`pyglet.window.Window.on_draw` event for all windows and uses :py:func:`pyglet.clock.tick` and :py:func:`pyglet.clock.get_sleep_time` on the default clock to determine the return value. This method should be overridden by advanced users only. To have code execute at regular intervals, use the :py:func:`pyglet.clock.schedule` methods. :rtype: float :return: The number of seconds before the idle method should be called again, or `None` to block for user input. on_drawFT) r update_timecall_scheduled_functionsrrQ_legacy_invalidinvalidrRr"flipget_sleep_time)rdt redraw_allrTs rrKzEventLoop.idles2Z # # % %Z88<< k / /F /f4 / /  """%%i000 ).&z((...rcx|j|j}|j|S)zFlag indicating if the event loop will exit in the next iteration. When set, all waiting threads are interrupted (see :py:meth:`sleep`). Thread-safe since pyglet 1.2. :see: `exit` :type: bool )rCacquire _has_exitrelease)rresults rrHzEventLoop.has_exits:  ((***  ((*** rc|j||_|j|jdSr )rCrgrhrri)rvalues rrHzEventLoop.has_exit sN  ((***  '')))  ((*****rcPd|_tjdS)zSafely exit the event loop at the end of the current iteration. This method is a thread-safe equivalent for for setting :py:attr:`has_exit` to ``True``. All waiting threads will be interrupted (see :py:meth:`sleep`). TN)rHrrJrrs rexitzEventLoop.exits&  &&(((((rc|j|j||j}|j|S)aWait for some amount of time, or until the :py:attr:`has_exit` flag is set or :py:meth:`exit` is called. This method is thread-safe. :Parameters: `timeout` : float Time to wait, in seconds. .. versionadded:: 1.2 :rtype: bool :return: ``True`` if the `has_exit` flag is set, otherwise ``False``. )rCrgwaitrhri)rr2rjs rsleepzEventLoop.sleepsQ  ((***  %%g...  ((*** rclttjdkr|dSdS)zDefault window close handler.rN)lenrrQrnrrTs ron_window_closezEventLoop.on_window_close1s0 s{  q IIKKKKK ! rcdS)aA window was closed. This event is dispatched when a window is closed. It is not dispatched if the window's close button was pressed but the window did not close. The default handler calls :py:meth:`exit` if no more windows are open. You can override this handler to base your application exit on some other policy. :event: Nr,rts rruzEventLoop.on_window_close7rcdS)zThe event loop is about to begin. This is dispatched when the event loop is prepared to enter the main run loop, and represents the last chance for an application to initialise itself. :event: Nr,rs rrFzEventLoop.on_enterErwrcdS)aThe event loop is about to exit. After dispatching this event, the :py:meth:`run` method returns (the application may not actually exit if you have more code following the :py:meth:`run` invocation). :event: Nr,rs rrGzEventLoop.on_exitOrwr)r;r<r=r>rCrhrrLrIrXrZrWrKpropertyrHsetterrnrqru_is_pyglet_doc_runrFrGr,rrr@r@sA  I   ###0---III"666 III%/%/%/N  X _++_+ )))* !           3!!rr@rurFrG)sysr platformrpygletrrrrhasattrrr|r EventDispatcherr@register_event_typer,rrrs>H """"""WS"566P3;PL L L L L L L L ^WWWWW%WWWt /000 j))) i(((((r