Problem (unresolved across 4 releases):
When copying an image and pasting it into a web app that treats the paste
as a file (Gemini, ChatGPT, uploaders), Chromium always assigned the same
fixed name 'imagen.png'. A second distinct image collided and the site
rejected it with 'la imagen imagen.png ya existe'. The name was invented by
Chromium, not the app, which is why adding/removing CF_HDROP changed nothing.
Fix:
SetImageToClipboard now also offers the image as a named virtual file with a
unique .png name (CFSTR_FILEDESCRIPTORW + CFSTR_FILECONTENTS) alongside
CF_DIBV5, via the plain SetClipboardData flow (no OLE). Chromium hands that
unique name to the uploader and the collision is gone. Inline paste (image
editors, rich-text) keeps taking the bitmap.
Validated in Gemini: two distinct images upload without error; inline OK.
Also includes:
- Copy icon in card hover actions (same action as the context menu).
- Self-write guard via GetClipboardOwner() (no longer drops external copies).
- processFiles ignores paths inside the internal images store.
Full Changelog: v2.6.2...v2.6.3