^ jL-RddlmZddlZddlZddlZddlmZmZmZddl m Z m Z m Z er ddl mZddlmZeedoejZGdd ZGd d e jZed ed eddS)) annotationsN) TYPE_CHECKINGAnyCallable)appclockevent)EventDispatcher) BaseWindowis_pyglet_doc_runc\eZdZdZddZddZdd ZddZddZddZ dddZ d dZ ddZ dS)!PlatformEventLoopzSAbstract class, implementation depends on platform. .. versionadded:: 1.2 returnNonecftj|_tj|_dSN)queueQueue _event_queue threadingEvent _is_runningselfs J/home/agentuser/manim-venv/lib/python3.11/site-packages/pyglet/app/base.py__init__zPlatformEventLoop.__init__s&!KMM$?,,boolc4|jS)zIf the event loop is currently processing. ``True`` if running, or ``False`` if it is blocked or not activated. )ris_setrs r is_runningzPlatformEventLoop.is_runnings &&(((r dispatcherr r strargsrch|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. N)rputnotify)rr"r r$s r post_eventzPlatformEventLoop.post_event!s3 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_eventrEmptyReferenceError)rr"evntr$s rdispatch_posted_eventsz(PlatformEventLoop.dispatch_posted_events0s   )-):)>)>u)E)E& D$) )$666666;   !      s,0A A Ac td)a Notify 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 afterward. abstractNotImplementedErrorrs rr'zPlatformEventLoop.notify?s"*---rcdSrrs rstartzPlatformEventLoop.startH rNtimeout None | floatc td)Nr1r2rr8s rstepzPlatformEventLoop.stepKs!*---rfuncrintervalfloatcdSrr5)rr=r>s r set_timerzPlatformEventLoop.set_timerNr7rcdSrr5rs rstopzPlatformEventLoop.stopQr7rrrrr)r"r r r#r$rrrr)r8r9rr)r=rr>r?rr) __name__ __module__ __qualname____doc__rr!r(r/r'r6r<rArCr5rrrrs----))))        ....    .....          rrceZdZdZdZdZd dZed!d Zd"d#d Z d dZ ed dZ d dZ d$dZ ed%dZejd&dZd dZd'dZd(dZerd(dZd dZd dZdSdS)) 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. NFrrctj|_tj|_d|_d|_dS)NF)r Condition_has_exit_conditionr get_defaultr! _intervalrs rrzEventLoop.__init__gs5#,#6#8#8 &(( rdtr?cNtjD]}||dSr)rwindowsdraw)rQwindows r_redraw_windowszEventLoop._redraw_windowsms0k  F KKOOOO  r?r> float | Nonec||_|nF|dkr |j|jn |j|j|d|_ddlm}d|_tj D]*}| | +tj }||dd|_|js0|}|||j0d|_|d|dS)aBegin processing events, scheduled functions and window updates. This method enters into the main event loop and, if the ``interval`` argument is not changed, schedules calling the :py:meth:`pyglet.window.Window.draw` method. You can change the ``interval`` argument to suit your needs. Args: interval: Windows redraw interval, in seconds (framerate). If ``interval == 0``, windows will redraw as fast as possible. This can saturate a CPU core, so do not do this unless GPU bound. If ``interval is None``, pyglet will not schedule calls to the :py:meth:`pyglet.window.Window.draw` method. Users must schedule this themselves for each Window (or call it on-demand). This allows setting a custom framerate per window, or changing framerate during runtime (see example in the documentation). This method returns when :py:attr:`has_exit` is set to True. IE: when :py:meth:`exit` is called. Developers are discouraged from overriding the ``run`` method, as the implementation is platform-specific. NrF)Windowon_enterTon_exit)rPrschedulerVschedule_intervalhas_exit pyglet.windowrZ_enable_event_queuerrS switch_todispatch_pending_eventsplatform_event_loopr6r+r!idler<rC)rr>rZrUrdr8s rrunz EventLoop.runssQ0"    ]] J   4 5 5 5 5 J ( ()=x H H H ((((((%*"k - -F        * * , , , ,!5!!### J'''- .iikkG  $ $W - - -- .  I&&&  """""rcx|}tj|j|dS)aCalled 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 N)rerrdrA_blocking_timerr;s renter_blockingzEventLoop.enter_blockings3))++ ))$*>HHHHHrcFtjdddS)z}Called by pyglet internal processes when the blocking operation completes. :see: :py:meth:`enter_blocking`. N)rrdrAr5rr exit_blockingzEventLoop.exit_blockings# ))$55555rc"|j}|j||j|||jd}t j|j |dS)NT) r update_timecall_scheduled_functionsrPrVget_sleep_timerrdrArh)rrQr8s rrhzEventLoop._blocking_timers Z # # % % ++B/// > !   $ $ $*++D11 ))$*>HHHHHrr9c|j}|j||jdS)acCalled 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. Returns: The number of seconds before the idle method should be called again, or ``None`` to block for user input. T)rrmrnro)rrQs rrezEventLoop.idlesE2Z # # % % ++B///z((...rrcx|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. )rNacquire _has_exitrelease)rresults rr_zEventLoop.has_exits:  ((***  ((*** rvaluec|j||_|j|jdSr)rNrrrsr'rt)rrvs rr_zEventLoop.has_exitsN  ((***  '')))  ((*****rcPd|_tjdS)zSafely exit the event loop at the end of the current iteration. This method is a thread-safe equivalent for setting :py:attr:`has_exit` to ``True``. All waiting threads will be interrupted (see :py:meth:`sleep`). TN)r_rrdr'rs rexitzEventLoop.exits&  &&(((((rr8c|j|j||j}|j|S)aWait for some amount of time. Waits until the :py:attr:`has_exit` flag is set or :py:meth:`exit` is called. This method is thread-safe. Args: timeout: Time to sleep, in seconds. .. versionadded:: 1.2 )rNrrwaitrsrt)rr8rus rsleepzEventLoop.sleep sQ  ((***  %%g...  ((*** rrUr clttjdkr|dSdS)zDefault window close handler.rN)lenrrSryrrUs ron_window_closezEventLoop.on_window_closes0 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. Nr5rs rrzEventLoop.on_window_close'rcdS)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. Nr5rs rr[zEventLoop.on_enter3rrcdS)zThe 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). Nr5rs rr\zEventLoop.on_exit;rrrD)rQr?rr)rW)r>rXrr)rr9rE)rvrrr)r8r?rr)rUr rr)rFrGrHrIrNrsr staticmethodrVrfrirkrhrepropertyr_setterryr|r_is_pyglet_doc_runr[r\r5rrrKrKUs  I \ 6#6#6#6#6#pIIII"666\6IIII////>   X _+++_+ ))))$               /rrKrr[r\) __future__rrsysrtypingrrrpygletrrr pyglet.eventr r`r hasattrr rrrKregister_event_typer5rrrsd"""""" //////////$$$$$$$$$$),,,,,,((((((WS"566P3;PA A A A A A A A Hlllll%lll^ /000 j))) i(((((r