InvokeAI/invokeai/app
psychedelicious bdfdf854fc fix: canvas not working on queue
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.
2023-09-20 09:57:10 -04:00
..
api feat: queued generation (#4502) 2023-09-20 15:09:24 +10:00
assets/images tweaks in response to psychedelicious review of PR 2023-07-26 15:27:04 +10:00
cli isort wip 2023-09-12 13:01:58 -04:00
invocations fix: canvas not working on queue 2023-09-20 09:57:10 -04:00
models feat(nodes): refactor parameter/primitive nodes 2023-08-16 09:54:38 +10:00
services fix: canvas not working on queue 2023-09-20 09:57:10 -04:00
util fix: canvas not working on queue 2023-09-20 09:57:10 -04:00
api_app.py feat: queued generation (#4502) 2023-09-20 15:09:24 +10:00
cli_app.py feat: queued generation (#4502) 2023-09-20 15:09:24 +10:00