Post by 0xAF on Oct 6, 2019 3:03:20 GMT -5
hi, I have two suggestions:
run batch fixes in sequence
I mean, you open the window, choose the batch fixes that you want to process and press RUN
so every change will be do only once per file
S4S: backup file > made a modification (all) > save
it will save time and disk space (no need for too many backups), plus if you use SSD - it saved it's lifespan
also "no backup" option will be cool too (yes, I have backed up all my CC and I don't need it at all)
and batch fix for... uncompress package
it's pretty easy to implement, since you are already re-writing package, you just uncheck the compression flag for all elements
for what?
for example I have a lot of free SSD space and poor CPU and limited in RAM
uncompressed package should consume less CPU time and memory to load and operate (in theory)
of course it's will increase I/O load, but if you have SSD it's doesn't matter
run batch fixes in sequence
I mean, you open the window, choose the batch fixes that you want to process and press RUN
so every change will be do only once per file
S4S: backup file > made a modification (all) > save
it will save time and disk space (no need for too many backups), plus if you use SSD - it saved it's lifespan
also "no backup" option will be cool too (yes, I have backed up all my CC and I don't need it at all)
and batch fix for... uncompress package
it's pretty easy to implement, since you are already re-writing package, you just uncheck the compression flag for all elements
for what?
for example I have a lot of free SSD space and poor CPU and limited in RAM
uncompressed package should consume less CPU time and memory to load and operate (in theory)
of course it's will increase I/O load, but if you have SSD it's doesn't matter
