Skip to content

Latest commit

 

History

History
44 lines (32 loc) · 1.32 KB

core.rst

File metadata and controls

44 lines (32 loc) · 1.32 KB

Core

Running

qtrio.run

qtrio.Runner

qtrio.Outcomes

Emissions

The basics of handling Qt GUIs is to respond to the widgets' signals being emitted. qtrio.enter_emissions_channel is the primary tool for handling this. It allows for connection of signals prior to showing a window and subsequent iteration of the emissions. See the emissions example <examples/emissions> for an example usage.

qtrio.enter_emissions_channel

qtrio.Emission

qtrio.Emissions

If you need a more Qt-like callback mechanism qtrio.open_emissions_nursery offers that. Instead of tossing the callbacks behind the couch where they can leave their errors on the floor they will be run inside a nursery.

qtrio.open_emissions_nursery

qtrio.EmissionsNursery

Helpers

qtrio.Signal

Reentry Events

Generally you should not need to use these functions. If you want to have control over when the Qt event type is registered, what value it gets, or handle any exceptions raised then you may like to call these directly.

qtrio.register_event_type

qtrio.register_requested_event_type

qtrio.registered_event_type