# [Bug] [High] Secondary Drag-and-Drop Images Fail to Import / Append to Active Image List #1239

Open
opened 2026-11-04 02:25:43 +00:00 by enjin2310 · 0 comments

Summary

Dragging and dropping additional image files onto the canvas while an initial image is loaded or being processed fails to append the new files to the active project list (IMAGES · 1).

Issue Description

In the desktop application view (Spiker Stack), after an initial image (e.g., shingeki.png) has been loaded into the project workspace, attempting to drag and drop a secondary image file onto the viewport drop target area ("Drop images, a folder, or a .sstack") yields no reaction. The newly dropped file is ignored, fails to register under the left sidebar (IMAGES panel), and does not append to the active stack list.

Environment

Property Value
Application Spiker Stack
Environment Production
Operating System Windows 11 - 25H2
Device Desktop
Language English

Preconditions

  • The application is open in desktop mode with an active session (Spiker Stack workspace).
  • At least one image is already imported and visible in the left panel list (e.g., shingeki.png).
  • The main canvas area displays the drag-and-drop overlay ("Drop images, a folder, or a .sstack").

Steps to Reproduce

  1. Open Spiker Stack and import an initial image file into the project.
  2. Verify that the imported image is listed under the Images tab on the left sidebar (IMAGES · 1).
  3. Drag a second image file from the host operating system file manager.
  4. Drop the second image file directly onto the central canvas drop target ("Drop images, a folder, or a .sstack").
  5. Observe the left Images panel and the project queue.

Expected Result

  • The secondary dragged image should be recognized, added to the project queue, and listed in the left sidebar (updating the counter to IMAGES · 2).
  • A subtle visual highlight or drop confirmation should notify the user that the additional image was successfully appended.

Actual Result

  • The dropped image is completely ignored.
  • The image list remains fixed at IMAGES · 1 without updating or loading the new file into the stack queue.

Evidence

  • Workspace Area: Drop target prompt ("Drop images, a folder, or a .sstack") displayed over the active canvas.
  • Sidebar State: IMAGES · 1 panel showing only the single initial file shingeki.png.
  • Status Bar: Bottom bar indicating "2 files are waiting until the current job finishes" or "Developing 1/1", pointing to queue handling or background thread execution blocks.

Impact

  • High / Functional Blocker: Users are unable to continuously build focus-stacking image series via intuitive drag-and-drop actions, forcing them to restart or use alternative import routes.

Frequency

Always

Reproducibility

100%

Notes & Recommendations

  • Inspect the drag-and-drop event handler (onDrop / File API listener) on the central viewport component to ensure file arrays append to existing state arrays rather than resetting or rejecting incoming payloads during ongoing background jobs (Developing 1/1).
  • Ensure non-blocking file queueing so additional drops populate the sidebar list immediately, even if processing is queued.
## Summary Dragging and dropping additional image files onto the canvas while an initial image is loaded or being processed fails to append the new files to the active project list (IMAGES · 1). ## Issue Description In the desktop application view (Spiker Stack), after an initial image (e.g., shingeki.png) has been loaded into the project workspace, attempting to drag and drop a secondary image file onto the viewport drop target area ("Drop images, a folder, or a .sstack") yields no reaction. The newly dropped file is ignored, fails to register under the left sidebar (IMAGES panel), and does not append to the active stack list. ## Environment | Property | Value | |-----------|--------| | Application | Spiker Stack | | Environment | Production | | Operating System | Windows 11 - 25H2 | | Device | Desktop | | Language | English| ## Preconditions - The application is open in desktop mode with an active session (Spiker Stack workspace). - At least one image is already imported and visible in the left panel list (e.g., shingeki.png). - The main canvas area displays the drag-and-drop overlay ("Drop images, a folder, or a .sstack"). ## Steps to Reproduce 1. Open *Spiker Stack* and import an initial image file into the project. 2. Verify that the imported image is listed under the *Images* tab on the left sidebar (IMAGES · 1). 3. Drag a second image file from the host operating system file manager. 4. Drop the second image file directly onto the central canvas drop target ("Drop images, a folder, or a .sstack"). 5. Observe the left *Images* panel and the project queue. ## Expected Result - The secondary dragged image should be recognized, added to the project queue, and listed in the left sidebar (updating the counter to IMAGES · 2). - A subtle visual highlight or drop confirmation should notify the user that the additional image was successfully appended. ## Actual Result - The dropped image is completely ignored. - The image list remains fixed at IMAGES · 1 without updating or loading the new file into the stack queue. ## Evidence - *Workspace Area:* Drop target prompt ("Drop images, a folder, or a .sstack") displayed over the active canvas. - *Sidebar State:* IMAGES · 1 panel showing only the single initial file shingeki.png. - *Status Bar:* Bottom bar indicating "2 files are waiting until the current job finishes" or "Developing 1/1", pointing to queue handling or background thread execution blocks. ## Impact - *High / Functional Blocker:* Users are unable to continuously build focus-stacking image series via intuitive drag-and-drop actions, forcing them to restart or use alternative import routes. ## Frequency Always ## Reproducibility 100% ## Notes & Recommendations - Inspect the drag-and-drop event handler (onDrop / File API listener) on the central viewport component to ensure file arrays append to existing state arrays rather than resetting or rejecting incoming payloads during ongoing background jobs (Developing 1/1). - Ensure non-blocking file queueing so additional drops populate the sidebar list immediately, even if processing is queued.
Sign in to join this conversation.