Kushal Kolar
Kushal Kolar
I just noticed a few things in the API docs were missing because we haven't run `generate_api.py` in a while, we should add commit hooks to the repo
When using arrays that should be lazily-read (such as from remote filesystems over a network), there should be an option to skip computing the min max of the entire array...
I just noticed we don't put the feature docs in the main doc page for each graphic, they are only within the constructor doc pages: https://github.com/fastplotlib/fastplotlib/blob/master/docs/source/api/graphics/ImageGraphic.rst
Right now the selection feature classes live inside `_features`, but they are quite strongly tied to their corresponding selector so we can just move it there. It's not like `PointsDataFeature`...
For example if user specifies gridplot shape of `(3, 3)` and passes in a 1D array or list of names, use `np.array().reshape(shape)`
maybe this is just the positions geometry buffer, need to check with line too
For example, use a dict of data `{str: array}`, the key is used for subplot names and titles, values used as the data. Does it make sense for any other...
Right now we have `Graphic` and `GraphicCollection`. It would be useful to have higher level objects for certain purposes. Examples: 1. Segmentation overlays when `LineGraphic` is not viable due to...