csehatt741

@dtslvr, I'll have a look!

@dtslvr, the icon is fetched via the backend API from external storage and it is not available locally. What should the mock return and `GfEntityLogoComponent` display in the story?

I wonder where the UI is configured to forward `https://localhost:4200/api/v1/logo` requests to the backend API?

@dtslvr, unfortunately, StoryBook stories cannot get images from `https://ghostfol.io`, as the browser throws a CORS related error: `NotSameOrigin`. The host's `cross-origin-resource-policy` - `same-origin` should be relaxed to `cross-origin` in order...

@lil-lilithhh Currently, parameters in the left panel are shared among all the tabs (generate, canvas, upscaling), while the multi-canvas feature, to provide higher degree of isolation between work in different...

I've created a related thread on Discord where ideas are discussed: [Multi-Canvas](https://discord.com/channels/1020123559063990373/1421801763832332398)

@psychedelicious, here is the current status of multi-canvas development and refactoring: - to limit the scope of refactoring I still kept the notion of the active canvas - it always...

Since there is always only one canvas rendered, the active one, so the `CanvasManager` is created and initialized when the canvas is displayed and destroyed when the canvas becomes inactive....

@psychedelicious Actually I've explicitly invested into migration, but even did not try it out with a clean install before. The root cause was missing canvas states in auxiliary canvas slices...

@psychedelicious, I've made the following progress based on your guidance: - refactored and merged slices: - merged canvas, params, settings, staging into `canvasSlice` - created `tabSlice` and merged loras, params...