Thanks to visit codestin.com
Credit goes to github.com

Skip to content

event_handling

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History
 
 

event_handling

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
README.txt
README.txt
 
 
close_event.py
close_event.py
 
 
coords_demo.py
coords_demo.py
 
 
cursor_demo.py
cursor_demo.py
 
 
data_browser.py
data_browser.py
 
 
figure_axes_enter_leave.py
figure_axes_enter_leave.py
 
 
ginput_manual_clabel_sgskip.py
ginput_manual_clabel_sgskip.py
 
 
image_slices_viewer.py
image_slices_viewer.py
 
 
keypress_demo.py
keypress_demo.py
 
 
lasso_demo.py
lasso_demo.py
 
 
legend_picking.py
legend_picking.py
 
 
looking_glass.py
looking_glass.py
 
 
path_editor.py
path_editor.py
 
 
pick_event_demo.py
pick_event_demo.py
 
 
pick_event_demo2.py
pick_event_demo2.py
 
 
poly_editor.py
poly_editor.py
 
 
pong_sgskip.py
pong_sgskip.py
 
 
resample.py
resample.py
 
 
timers.py
timers.py
 
 
trifinder_event_demo.py
trifinder_event_demo.py
 
 
viewlims.py
viewlims.py
 
 
zoom_window.py
zoom_window.py
 
 

README.txt

.. _event_handling_examples:

Event handling
==============

Matplotlib supports :doc:`event handling</users/explain/event_handling>` with
a GUI neutral event model, so you can connect to Matplotlib events without
knowledge of what user interface Matplotlib will ultimately be plugged in to.
This has two advantages: the code you write will be more portable, and
Matplotlib events are aware of things like data coordinate space and which
axes the event occurs in so you don't have to mess with low level
transformation details to go from canvas space to data space.  Object picking
examples are also included.