You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CLCL is very useful, thanks for making it.
I used it for many years and observed what history comes to use and what is dead weight, wasting disk writes and space.
I tried to configure limits I wanted via existing settings in CLCL v2.1.1 and could not, even found a bug, I will post it as separate issue, #5.
Settings like in this example picture would enable what I wanted (I will write below), and also simplify my current working config to 3 line table with different limits and toggles.
Best variant (from user view) is at bottom.
What I want to set up:
Ignore everything along with a DROP FILE LIST. Currently this is simple and works well. A list of file names was never useful to me, because if I want, I can get it explicitly in a 3rd party file manager program with/without paths and metadata (dates, sizes, etc), but keeping it every time I cut/paste files was a waste.
Save everything along with a BITMAP, limited to 1 GB and only to memory, not disk. Currently it works, but requires to add filter rules atop with appended format names that may exist or not. For example, copying layers or vector drawings in SAI to be pasted from history in a working form.
Save TEXT and/or UNICODE TEXT and ignore anything else along with them. Currently it works, but requires 3 lines of rules (text + unicode, only unicode, only text). Also I wanted texts below 50-100 KB to be saved to history in memory and to disk, and over 50-100 KB - only in memory. I could not make it work and found a bug [Bug report] Filter rules with duplicate format name lines may cause empty history file on disk #5. Usually a text of big size is a content of entire file or a web page. They may be useful for saving or comparison, but not to keep between reboots. I have set the number of items to keep to around as much as my display area allows (774) to remember what I was doing, etc. Sometimes I can forget what I was planning to do even 5 seconds ago, and history of copypaste can help. But because of this, big items can linger for days. I manually delete big data in history as soon as I am done working with it, to keep memory/disk usage lower. Big disk write in this case is a waste.
The text was updated successfully, but these errors were encountered:
Hello.
CLCL is very useful, thanks for making it.
I used it for many years and observed what history comes to use and what is dead weight, wasting disk writes and space.
I tried to configure limits I wanted via existing settings in CLCL v2.1.1 and could not, even found a bug, I will post it as separate issue, #5.
Settings like in this example picture would enable what I wanted (I will write below), and also simplify my current working config to 3 line table with different limits and toggles.
Best variant (from user view) is at bottom.
What I want to set up:
DROP FILE LIST
. Currently this is simple and works well. A list of file names was never useful to me, because if I want, I can get it explicitly in a 3rd party file manager program with/without paths and metadata (dates, sizes, etc), but keeping it every time I cut/paste files was a waste.BITMAP
, limited to 1 GB and only to memory, not disk. Currently it works, but requires to add filter rules atop with appended format names that may exist or not. For example, copying layers or vector drawings in SAI to be pasted from history in a working form.TEXT
and/orUNICODE TEXT
and ignore anything else along with them. Currently it works, but requires 3 lines of rules (text + unicode, only unicode, only text). Also I wanted texts below 50-100 KB to be saved to history in memory and to disk, and over 50-100 KB - only in memory. I could not make it work and found a bug [Bug report] Filter rules with duplicate format name lines may cause empty history file on disk #5. Usually a text of big size is a content of entire file or a web page. They may be useful for saving or comparison, but not to keep between reboots. I have set the number of items to keep to around as much as my display area allows (774) to remember what I was doing, etc. Sometimes I can forget what I was planning to do even 5 seconds ago, and history of copypaste can help. But because of this, big items can linger for days. I manually delete big data in history as soon as I am done working with it, to keep memory/disk usage lower. Big disk write in this case is a waste.The text was updated successfully, but these errors were encountered: