Options
Clipboard history
- Clipboard history
-
Clipboard history
Jean Lalonde > 2023-02-04 14:32
Suggestion from a joeNOR's thread. Also discussed with Mike:
(JL: 2023-02-04) I'm first trying to see if the existing Clipboard history tools could be used in complementarity with QCE. But I had little success testing it with Windows history tool and Ditto. In both case, when QCE is in synced mode, the selected item in the history is pasted twice in QCE.
In my understanding, the history tools does two things:
1) it updates the Clipboard and
2) it sends (or types) the selected item to the target window.
I'm not sure in what order but the end result is the same in QCE: the selected content is added twice to the editor:
1) When the Clipboard is changed the editor is changed to reflect the Clipboard content
2) The history tool sends the content to the target window again (using a command similar to the "Send" command in AHK). -
RE: Clipboard history
Jean Lalonde > 2023-02-10 14:47
Following some tests with existing Clipboard history tools, my conclusion is that it is better for QCE to use an internal history database. At first, this will be a quite rudimentary history tool with buttons on both side to move back and forth in the last Clipboard clips of type text (not images, binaries, etc.).
![[Image: 0yxobmj.png]](https://i.imgur.com/0yxobmj.png)
I assume users wanting more elaborate features will continue to use their preferred Clipboard history tool.
Data will be stored in a SQLite database (a reliable technology well used in QAP). -
RE: Clipboard history
joeNOR > 2023-02-16 14:27
Jean, I totally agree.
Should you at some point in time decide to make a history function, make it totally INdependent of any functions in Windows.
If you store it in a SQLite DB, yay!
Knowing you, QCE could be a great tool, stay far away from default functions.
My $0.02
Regards,
joeNOR
Edit:
This was the point of some of my early ramblings about QCE and history.
Make it self contained and QCE would be a killer tool, imho. -
RE: Clipboard history
Jean Lalonde > 2023-02-16 14:50
Hi Joe,
Not sure I get your points. Could you elaborate (here or by email)
> make it totally INdependent of any functions in Windows.
Of course, the feature is linked to an event in Windows fired when the Clipboard changes. QCE will react to this change when the content type is text.
> stay far away from default functions.
What default functions? -
RE: Clipboard history
joeNOR > 2023-02-16 16:17
Sorry for being unclear!
My point is, make it stand alone, then interface with Windows functions.
A forum post may not be the perfect medium to convey the point.
I could write about API's and isolation, but I think you are on the right path.
I'll send you an email if you want.
-jN
Edit:
Basically it is like this.
THE USER
|
|
QCE, self contained, including history
|
| Interface to the function in the OS
|
Windows Clipboard function or whatever
|
| Basic level interface (not user, ring 0)
|
The operating system -
RE: Clipboard history
Jean Lalonde > 2023-02-16 16:28
I think I got your point. You would not want, for example, to see QCE rely on the Windows 10 Clipboard history or another history tool.
I want QCE to be "other history tools friendly" but it will not depend on them. -
RE: Clipboard history
joeNOR > 2023-02-16 16:34
Thank you!
Yes, QCE should be highly independent. Be its own entity.
Then...use functions in the OS.
-jN
Edit:
Jean, I know I am pain in the ......
Shoot me an email if you want.