Description
I have some old VBA macros that operate on CAD documents (not AutoCAD). These macros activate one document, locate a specific entity, execute Selection.Copy, switch to another document, and then execute Selection.Paste.
I think that the CAD application uses a temporary file to handle clipboard data—placing only some metadata into the clipboard—but I don't know how to confirm this:
- The copy operation creates a file containing the entities to paste and places a metadata clip in the clipboard.
- The paste operation checks the clipboard, and if everything is consistent, loads the file into the active document.
These macros have worked reliably for over 20 years. However, after installing CopyQ, the paste occasionally fails. The failure rate is lower if I avoid interacting with the system—about 5%—but increases significantly (up to ~20%) when I perform unrelated actions, such as clicking a link in a browser.
I added some code to detect paste failures. When detected, the macro pauses, allowing me to manually re-trigger the paste and continue execution during debugging. While this isn't a suitable workaround for production, my development machine doesn't typically handle production tasks, so it's manageable for now.
I've used this macro setup for years:
- No clipboard manager initially
- Then ClipClip for about 3 years
- Only recently switched to CopyQ, and that's when the issue started
So yeah, here’s a bug report that only happens on my machine, while debugging VBA macros interacting with a custom CAD application. How do you even fix that?
Any suggestions?
CopyQ 9.1.0 on Windows 10