o îÇ hLã@sŒdZddlmZddlmZddlmZmZmZm Z ddl m Z Gdd„de ƒZ Gdd „d eƒZ Gd d „d eƒZGd d „d eƒZeZeZdS)aâ A fully functional, do-nothing backend intended as a template for backend writers. It is fully functional in that you can select it as a backend e.g. with :: import matplotlib matplotlib.use("template") and your program will (should!) run without error, though no output is produced. This provides a starting point for backend writers; you can selectively implement drawing methods (`~.RendererTemplate.draw_path`, `~.RendererTemplate.draw_image`, etc.) and slowly see your figure come to life instead having to have a full-blown implementation before getting any results. Copy this file to a directory outside the Matplotlib source tree, somewhere where Python can import it (by adding the directory to your ``sys.path`` or by packaging it as a normal Python package); if the backend is importable as ``import my.backend`` you can then select it using :: import matplotlib matplotlib.use("module://my.backend") If your backend implements support for saving figures (i.e. has a ``print_xyz`` method), you can register it as the default handler for a given file type:: from matplotlib.backend_bases import register_backend register_backend('xyz', 'my_backend', 'XYZ File Format') ... plt.savefig("figure.xyz") é)Ú_api)ÚGcf)ÚFigureCanvasBaseÚFigureManagerBaseÚGraphicsContextBaseÚ RendererBase)ÚFigurecsdeZdZdZ‡fdd„Zddd„Zdd„Zdd d „Zd d „Zdd„Z dd„Z dd„Z dd„Z ‡Z S)ÚRendererTemplatezò The renderer handles drawing/rendering operations. This is a minimal do-nothing class that can be used to get started when writing a new backend. Refer to `.backend_bases.RendererBase` for documentation of the methods. cstƒ ¡||_dS©N)ÚsuperÚ__init__Údpi)Úselfr ©Ú __class__©úx/var/www/html/construction_image-detection-poc/venv/lib/python3.10/site-packages/matplotlib/backends/backend_template.pyr 0s  zRendererTemplate.__init__NcCódSr r)rÚgcÚpathÚ transformÚrgbFacerrrÚ draw_path4ózRendererTemplate.draw_pathcCrr r)rrÚxÚyÚimrrrÚ draw_imageOrzRendererTemplate.draw_imageFc Crr r) rrrrÚsÚpropÚangleÚismathÚmtextrrrÚ draw_textRrzRendererTemplate.draw_textcCódS)NTr©rrrrÚflipyUózRendererTemplate.flipycCr$)N)édr(rr%rrrÚget_canvas_width_heightYr'z(RendererTemplate.get_canvas_width_heightcCr$)N)ér*r*r)rrrr!rrrÚget_text_width_height_descent]rz.RendererTemplate.get_text_width_height_descentcCstƒSr )ÚGraphicsContextTemplater%rrrÚnew_gc`szRendererTemplate.new_gccCs|Sr r)rÚpointsrrrÚpoints_to_pixelsdr'z!RendererTemplate.points_to_pixelsr )FN)Ú__name__Ú __module__Ú __qualname__Ú__doc__r rrr#r&r)r+r-r/Ú __classcell__rrrrr 's   r c@óeZdZdZdS)r,aì The graphics context provides the color, line styles, etc. See the cairo and postscript backends for examples of mapping the graphics context attributes (cap styles, join styles, line widths, colors) to a particular backend. In cairo this is done by wrapping a cairo.Context object and forwarding the appropriate calls to it using a dictionary mapping styles to gdk constants. In Postscript, all the work is done by the renderer, mapping line styles to postscript calls. If it's more appropriate to do the mapping at the renderer level (as in the postscript backend), you don't need to override any of the GC methods. If it's more appropriate to wrap an instance (as in the cairo backend) and do the mapping here, you'll need to override several of the setter methods. The base GraphicsContext stores colors as an RGB tuple on the unit interval, e.g., (0.5, 0.0, 1.0). You may need to map this to colors appropriate for your backend. N©r0r1r2r3rrrrr,mór,c@r5)ÚFigureManagerTemplatea" Helper class for pyplot mode, wraps everything up into a neat bundle. For non-interactive backends, the base class is sufficient. For interactive backends, see the documentation of the `.FigureManagerBase` class for the list of methods that can/should be overridden. Nr6rrrrr8‹r7r8c@s>eZdZdZeZdd„Ziej¥ddi¥Zdd„Z dd „Z d S) ÚFigureCanvasTemplatea2 The canvas the figure renders into. Calls the draw and print fig methods, creates the renderers, etc. Note: GUI templates will want to connect events for button presses, mouse movements and key presses to functions that call the base class methods button_press_event, button_release_event, motion_notify_event, key_press_event, and key_release_event. See the implementations of the interactive backends for examples. Attributes ---------- figure : `~matplotlib.figure.Figure` A high-level Figure instance cCst|jjƒ}|j |¡dS)aE Draw the figure using the renderer. It is important that this method actually walk the artist tree even if not output is produced because this will trigger deferred work (like computing limits auto-limits and tick values) that users may want access to before saving to disk. N)r Úfigurer Údraw)rÚrendererrrrr;«s zFigureCanvasTemplate.drawÚfoozMy magic Foo formatcKs | ¡dS)a{ Write out format foo. This method is normally called via `.Figure.savefig` and `.FigureCanvasBase.print_figure`, which take care of setting the figure facecolor, edgecolor, and dpi to the desired output values, and will restore them to the original values. Therefore, `print_foo` does not need to handle these settings. N)r;)rÚfilenameÚkwargsrrrÚ print_foo¾s zFigureCanvasTemplate.print_foocCr$)Nr=rr%rrrÚget_default_filetypeÊrz)FigureCanvasTemplate.get_default_filetypeN) r0r1r2r3r8Ú manager_classr;rÚ filetypesr@rArrrrr9•s r9N)r3Ú matplotlibrÚmatplotlib._pylab_helpersrÚmatplotlib.backend_basesrrrrÚmatplotlib.figurerr r,r8r9Ú FigureCanvasÚ FigureManagerrrrrÚs   F ?