mirror of
https://github.com/invoke-ai/InvokeAI
synced 2024-08-30 20:32:17 +00:00
bdfdf854fc
Add `batch_id` to outbound events. This necessitates adding it to both `InvocationContext` and `InvocationQueueItem`. This allows the canvas to receive images. When the user enqueues a batch on the canvas, it is expected that all images from that batch are directed to the canvas. The simplest, most flexible solution is to add the `batch_id` to the invocation context-y stuff. Then everything knows what batch it came from, and we can have the canvas pick up images associated with its list of canvas `batch_id`s. |
||
---|---|---|
.. | ||
config | ||
invocation_cache | ||
models | ||
session_processor | ||
session_queue | ||
shared | ||
__init__.py | ||
board_image_record_storage.py | ||
board_images.py | ||
board_record_storage.py | ||
boards.py | ||
default_graphs.py | ||
events.py | ||
graph.py | ||
image_file_storage.py | ||
image_record_storage.py | ||
images.py | ||
invocation_queue.py | ||
invocation_services.py | ||
invocation_stats.py | ||
invoker.py | ||
item_storage.py | ||
latent_storage.py | ||
model_manager_service.py | ||
processor.py | ||
resource_name.py | ||
sqlite.py | ||
thread.py | ||
urls.py |