When I set scrubbing mode to "Auto-scrub all except on double-copy" and copy text that needs scrubbing with ctrl-c and immediately paste it with ctrl-v it works as advertised, and get the cleanly scrubbed text .

But when I select the text from the history it pastes the dirty un-scrubbed text.

This doesn't happen in the other scrub modes.

Also had this problem back then with Version 4.2, now (v5.2.1) it acts more different within both 'Double-Copy' modes, as it adds one additional unscrubbed item when the option "Show Clipboard changes made by ClipboardFusion" is enabled, that should be no problem as the first/active item can be pasted with scrubbed text, but when you want choose it later from the Clipboard Manager it's not quite clear which of the doubled item is the scrubbed one (usually the upper in the list).

Yet when the said option is disabled, the original posted issue occurs: You are able to paste the scrubbed text right away, but in the history/Clipboard Manager it's only available as unscrubbed version, which has to be 'triggered' once again to get the scrubbed text/item back. (Fortunately there's a HotKey for this purpose, though a setting would be useful to choose if you want the text to remain scrubbed inside the history or just for the current/next paste-operation.)

Another (concerning) problem: When the 'Enabled Except on Double-Copy' Trigger-mode is active only CTRL+C copy/clipboard actions are recognized (for Scrub/Replace-Triggers). So when you single-copy lines of text (exceptionally) with the mouse/context menu, or other variants (e. g. the function 'goDoCommand("cmd_copy")' from Firefox), nothing will be scrubbed. Hopefully that can be changed/fixed for this mode, so it behaves normally like 'Enabled on Copy', except on Double-Copy event of course. I'd rather stick with this mode than always switch between the different modes or disable CF when not modified text/clipboard is required.

The 'double-entries' occur with the enabled "Show Clipboard changes made by ClipboardFusion" option when the 'Enabled on Double-Copy' or 'Enabled Except on Double-Copy' mode is active/used and affects every program, e. g. Windows Explorer or Notepad, also with all other applications closed. (Windows 7 64-bit, additionally tested in a VM with newly installed Framework v4.7.1.)

The capture and scrubbing of other clipboard-modifiers is working now, yet the initial problem and the creation of double-entries still persists. It is important to use 'Quick Clipboard History Select' or select the text-entry directly from the Clipboard History to reproduce the mentioned issue with the not scrubbed text-paste/insertion.

Actually it's noticeable right after you use CF for the first time or reset its settings and change to 'Enabled on Double-Copy' mode. Just double-copy text including selected spaces at the beginning and/or end.

When "Show Clipboard changes made by ClipboardFusion" is disabled (non-default) the OP described problem occurs instead.

Alright, then this leaves open the question why the results of the scrub is still stored, thus not ignored, when 'Enabled on Copy' is active. So probably this has to be changed instead, to stay consistent with the described 'do not show changes' setting.

Guess I'll need to get used to the enabled 'Show changes' options behaviour when that's gonna be fixed, which wouldn't matter that much now, since the standard 'insert multiple clipboard-entries in (chronological) order' macro still works (at least when Double-Copy isn't used).

On the other hand one 'Store/show clipboard scrubs/changes in Clipboard History' and another/separate 'Keep Clipboard History index after item/entry selection' would give some more control and adaptability depending on the type/scenario of applied 'clipboard management'.

Furthermore every time you 'copy' empty strings (nothing selected/marked when you do the copy command) with keystrokes (CTRL+C/CTRL+Ins) it runs the triggers over the current clipboard. Even when you clear the history before and then copy 'nothing' the current clipboard content will be added 'trigger-treated' to the history. Once again only with both 'Double-Copy' modes enabled, with 'Enabled on Copy' CF does nothing when nothing/no content is copied, as it's supposed to be. (This happens when you're running a background-program which sends the copy-command for every double-click - in case you're wondering why someone would press the copy-keystroke when actually nothing is selected to be copied.)

The double-copy behaviour you reproduced was already explained by your previous post (#12). I'm currently trying to address your "this is by design" statements regarding the second mode 'Enabled on Copy' (post #13).

"scrubbing happening even with no text selected" and "but the History ignores the result of that scrub, because that option is disabled" only applies to modes 'Enabled on Double-Copy' and 'Enabled Except on Double-Copy' but not to 'Enabled on Copy'.

Reproduce first "contradiction":
1. Disable Trigger Commands/Scrubbing
2. Copy text with white space before and after
3. Activate 'Enabled on Copy'
4. Paste clipboard-content to check the remaining spacing
5. Be sure to select/mark nothing that could replace/fill the current clipboard
6. Press Ctrl+C and then paste text (or select from history)
-> Result: Contrary to mentioned 'default design' clipboard is still not scrubbed
In my opinion the resulting behaviour (-> no unintended scrubbing) should be default for every mode, otherwise both 'Run Triggers on Clipboard text now' actions are kinda useless and unnecessary.

Reproduce second one (quoted):
1. Disable option 'Show Clipboard changes made by ClipboardFusion'
2. Activate 'Enabled on Copy'
3. Copy text with white space before and after
4. Paste clipboard-content to check the scrubbed/removed spacing
5. Select/paste item/text from Clipboard History list
6. Repeat step 035 with different examples
-> Result: The clipboard-entries are available in scrubbed condition within the History list, thus the scrub-result is maintained and certainly not 'ignored' (as opposed to the other two 'exceptional/conditional' scrubbing/trigger modes).
Again this (personally) would be the preferred resulting behaviour, also for the other modes, because when I consciously decide to scrub text with double-copy, it should be reasonable and expected that these text-entries remain scrubbed and can be accessed normally from the History list.

To summarize the previous question (from post #13): Why is there different design/handling of text-scrubbing and the results (in the way the clipboard itself is processed and stored) between the three trigger-modes? Can this be changed/optimized as described above, or could the separated options be implemented (see end of post #13)?

Glad to see this is reported and will probably result in more consistency between/regarding all trigger modes.


That's the point: According to your previous post, this ('still being the unscrubbed original text') shouldn't be possible or wanted (by design). So my suggestion was to apply this 'Enabled on Copy' text-preserving behaviour to the other trigger modes as well.

Would it be possible to bypass this predefined behaviour for the 'Enabled Except on Double-Copy' mode with the "Double Copy Sensitivity Lowbound/Highbound" or some other advanced setting as customizable alternative to prevent false double-copy actions?