enable
enable copied to clipboard
enthought
Enable: low-level drawing and interaction
It looks like the Celiagg backend starts out with a completely transparent image, but the Image/agg backend starts out filled with white. It looks like Quartz and Cairo also start...
For Kiva backends which store values in a buffer, we'd like a standard way to access the bytes as a buffer (ideally as a NumPy array). Many backends have `bmp_array`...
Possibly others as well. Some Chaco code presumes the existence of this method.
**Description:** When running demo [enable/enable/examples/demo/savage/buttons_on_canvas](https://github.com/enthought/enable/blob/main/enable/examples/demo/savage/buttons_on_canvas.py), a exception will happen in libc++: ``` 2023-04-06 11:25:18.884 Python[3819:77967] ApplePersistenceIgnoreState: Existing state will not be touched. New state will be written to /var/folders/2z/kylzj9s92y71cxscmljmpqrh0000gt/T/org.python.python.savedState libc++abi:...
**Problem Description** Some examples involving enable/enable/qt4/scrollbar.py can be run successfully, but after closing, an already deleted error will arise. **Reproduction Steps:** ``` python enable/enable/examples/demo/enable/scrolled_canvas_demo.py ``` Then close the plot window...
This is largely backwards compatible, because we are aliasing to the original constant names, but it does remove constant names from `kiva.__init__`. People probably shouldn't have been using that instead...
Doesn't draw anything it seems. Possibly an issue around image scaling. Also looks like the image drawing may not be clean in the context's state.
- [ ] verify all examples in https://github.com/enthought/enable/tree/main/enable/examples and https://github.com/enthought/enable/tree/main/kiva/examples run as expected - [ ] verify the intergration with etsdemo (see traitsui)
Ref: enthought/chaco#858 * `pyparsing` is already an optional dependency of `enable` * We should consider moving `enable.savage` to a new `savage` top-level package.
