[bug]: multiple delete

[VeyDlin]

Is there an existing issue for this?

• I have searched the existing issues

OS

Windows

GPU

cuda

VRAM

11

What version did you experience this issue on?

3.3.0

What happened?

If you select several images and press the delete key on the keyboard then this will work only for one image

Screenshots

No response

Additional context

No response

Contact Details

No response

[psychedelicious]

I'm not sure if this is really a bug.

The delete handler is in invokeai/frontend/web/src/features/gallery/components/CurrentImage/CurrentImageButtons.tsx, which isn't available when the those buttons are not mounted.

Let's first explore what the behaviour should be for combinations of these states:

• Gallery open or closed
• single or multiple images selected
• current image buttons visible or hidden (e.g. you are on canvas or workflow editor)

What is the desired behaviour in each combination?

[VeyDlin]

I'm not sure if this is really a bug.

This is contrary to UX, users are used to pressing the delete key to delete all selected objects, this happens in any software with a browser or operating system explorer

I was very upset when I realized that my painstaking work on selecting hundreds of images had simply disappeared because I was counting on deleting everything by pressing the delete key

[psychedelicious]

Sorry you lost your selection.

There's some miscommunication. It's not a good UX, I agree, but also it's not a "bug" - it's doing exactly what it's supposed to do - delete the current image. But when you have many images selected, this is not the expected behaviour.

It's not clear what the expected behaviour is, hence my probing question. Do you have any ideas for my question?

[VeyDlin]

This function should delete all selected images

The problems that you described are solved by adding an active widget focus (gallery, canvas, ...), the focus is set to the last widget that the user interacted with

An example of how this works can be seen in visual studio code, files in explorer can be selected and deleted, but if you click on the window with the code the focus switches but the selection in explorer does not disappear, in this case keystrokes will no longer be processed by the explorer (until the user returns focus)