I can use all other functions, but sending a active selection in photopea to "inpaint upload" doesn't work. I deactivated my other extensions and restarted A1111, but that didn't change anything This both doesn't work on Opera and Chrome Browser under Windows 11 for me

Using a mouse when trying to "paint" delicate forms can get quite cumbersome fast. I would like to suggest to support pens and tablets like we use in Photoshop. If necessary even as a checkbox option to switch on and off. Would be really great! 🙂

Seems not to send anything to ControlNet in the latest versions using the "Send to" buttons. Send to Img2Img & Send to Extras seem to be working fine.

Thanks for your work.

Add the button to send from upscale tab to photopea. It would have been extremely nice if that button had been there. Right now I only see the button from the photopea tab in extras. If there was a send button from extras, this case would work:

txt2img -> photopea(edit some part) -> extras -> back to photopea with upscaled image.

I can't send the image over to inpaint.

all the other buttons work such as:

1. send to img2img controlnet
2. send to extras
3. send to txt2img controlnet
4. send to img2img

inpaint selection I get a "no selection in active document"

https://github.com/yankooliveira/sd-webui-photopea-embed/assets/128274207/7d16cced-e988-43e3-941b-fa0ae47691aa

Selection is often short-lived, and users generally have less control on the selection than mask on an image. Should we consider use the actual mask attached to the image in Photopea as the inpaint mask in A1111?

Following code has issue checking whether a layer is of type LayerSet.

    // Gets all layers recursively, including the ones inside folders.
    function getAllArtLayers (document, layerCollection){
        for (var i = 0; i < document.layers.length; i++){
            var currentLayer = document.layers[i];
            if (currentLayer.typename === "ArtLayer"){
                layerCollection.push(currentLayer);
            } else {
                getAllArtLayers(currentLayer, layerCollection);
            }
        }
        return layerCollection;
    }

There are many other layer types other than ArtLayer and LayerSet:

1. ArtLayer: This is the most basic type of layer, containing raster images, text, or solid colors.

2. LayerSet: A layer set, or a group of layers, which can contain other ArtLayers or LayerSets.

3. TextItem: This represents a text layer. It is not a type of layer by itself, but an object contained in an ArtLayer that you can manipulate if the ArtLayer.kind property is LayerKind.TEXT.

4. SolidFill: This represents a solid color fill layer. Similar to TextItem, it's an object you would manipulate if ArtLayer.kind is LayerKind.SOLIDFILL.

5. SmartObjectLayer: This represents a Smart Object layer. Smart Objects are layers that contain image data from raster or vector images, and they preserve an image’s source content with all its original characteristics.

6. AdjustmentLayer: This represents an adjustment layer. Adjustment layers are used to apply color and tonal adjustments without permanently changing the underlying pixel values.

So if any of those layers appears on the canvas but don't have layers defined on them, the program will error out.

Here are some new control net features instructions. https://github.com/Mikubill/sd-webui-controlnet/discussions/1464 The above functionality shows how to use Controlnet to mimic Adobe Firefly Generative Fill.

As a replacement for Adobe Firefly Generative Fill, how about adding the ability to send the same functionality as inpaint selection to text to image control net?

Currently, Controlnet's masking capabilities are clearly limited to completely masking the desired area.

In the photopea-bindings.js file at line 32, this code generates the [Send to Photopea] button:

function createSendToPhotopeaButton(queryId, gallery) {
    const existingButton = gradioApp().querySelector(`#${queryId} button`);
    const newButton = existingButton.cloneNode(true);
    newButton.id = `${queryId}_open_in_photopea`;
    newButton.textContent = "Send to Photopea";
    newButton.addEventListener("click", () => openImageInPhotopea(gallery));
    gradioApp().querySelector(`#${queryId}`).appendChild(newButton);
}

It clones the first button inside #${queryId}, which is [Open images output directory] button.

When using the --hide-ui-dir-config parameter, this button is hidden, and the cloned [Send to Photopea] button is also hidden.

Set display to "flex" in createSendToPhotopeaButton should solve this problem:

newButton.style.display = "flex";

My laptop's screen resolution is 2560x1440. So I need to load pages in FF in 133%. And I don't see the layers panel. Only the canvas and the left side of photopea. Even if I toggle page width resizing the window, Photopea will not resize its frame.

If I reload my webui in 100% scale and open Photopea then all works fine. Even if I rescale it back in 133% - I see all the Photopea panels in 133%.

Is it possible to change the frame width or something like that? :-)

I found this bug when I am developing https://github.com/huchenlei/stable-diffusion-ps-pea.

Steps to reproduce:

• Set photopea in following state with a folder invisible, and select the folder or anything inside the folder.
• Click send to inpaint mask. You can see that the mask is not properly captured.

For comparison, if you select a top level layer and perform the same action:

The issue is caused by original code does not account LayerSet's visibility. For an ArtLayer to be visible on canvas, all it's parent's visibility all need to be true.

By default, add layer to add layer in current LayerSet if the activeLayer is a layerset or add a layer at the same level of the current active layer. So if we select the invisible folder layer, the new temp mask layer is added in the folder.

This PR port my implemenetation of exportSelectedLayerOnly from https://github.com/huchenlei/stable-diffusion-ps-pea, with extra feature of specifying export format and having a callback function to select which layer to export.

My main language is Chinese, so I have been using [bilingual-localization] to display both Chinese and English.

In the file photopea-bindings.js, at line 63, the [Inpaint selection] button get Inpaint tab using the following code:

Array.from(allButtons).find(button => button.textContent === 'Inpaint upload ');

However, [bilingual-localization] changes the value of textContent to '修復上傳 Inpaint upload ', which causes [Inpaint selection] can't find the Inpaint tab and therefore not work correctly.

In my own copy, I have modified it to:

Array.from(allButtons).find(button => button.textContent.endsWith('Inpaint upload '));

This works fine for me, but there might be other users who did not using bilingual-localization but the original localization feature of SD-WebUI. This could result in the disappearance of the latter part of 'Inpaint upload ', leaving only the text in another language. Using 'endsWith' might not be a solution for them.

Is there a more precise way to get Inpaint tab that avoids the localization break [Inpaint selection] functionality?