Total Commander

Transferring *.br2 files to another directory. Really?

d:\Total Commander\BAR\audio.bar
d:\Total Commander\BAR\photo.bar
d:\Total Commander\BAR\video.bar

d:\Total Commander\TEMP\audio.br2
d:\Total Commander\TEMP\photo.br2
d:\Total Commander\TEMP\video.br2
d:\Total Commander\TEMP\tcthumbs.db
d:\Total Commander\TEMP\tcthumbs.frl
d:\Total Commander\TEMP\tcthumbs.idb

AFAIK: This is not possible, both *.bar and *.br2 must be in the same folder

Yes I know it. This is for the future. Request.

What the heck should this feature be good for, please???
Each .bar file and its accompanying .br2 file form a pair. What should be the good of separating the two and scattering them across different folders?

karlchen,

One of the reasons is to divide read-only data and temporary data - i.e. if user have program folder with BAR files he may specify full-access temporary folder for BR2 files.

Second reason - if folder doesn't contain garbage, user can simply backup it w/o clearing before operation.

Thanks for your support, MVV.

MVV wrote:Second reason - if folder doesn't contain garbage, user can simply backup it w/o clearing before operation.

But BR2-Files are NOT garbage they are needed to display your bars.

Theese files are just cache files and not user data files. If file is broken/absent, TC just recreates it w/o any data loss.

MVV wrote:One of the reasons is to divide read-only data and temporary data - i.e. if user have program folder with BAR files he may specify full-access temporary folder for BR2 files.
Second reason - if folder doesn't contain garbage, user can simply backup it w/o clearing before operation.

Thank you, MVV, for doing what the requestor should have do done, provide a reason why Christian should change his programme.

By the way, the .BAR file(s) should not be read-only as a rule, unless you wish to prevent the T.C. user from changing his/her buttonbar(s).
You are right, in order to transfer a buttonbar, transferring the appropriate .BAR file and activating it on the target machine is sufficient. T.C. will (re)create the accompanying .BR2 file. Nevertheless I have never considered the .BR2 files garbage.

It is possible already today to put all .BAR files and the accompanying .BR2 files into a decidcated folder. Thus they will not fill the T.C. programme folder, in case you like to keep it clean.
Therefore going a step further and separating .BAR and .B2 files does not seem to make much of a difference to me.
Hence, I am not against an option to do so, just indifferent. If it will be possible in a future, fine. If not, fine, too. Could not care less.

Karl

*.BR2 files are not garbage because in different machine, you still see the button's icons (as far as you didn't change the accompanying *.bar file) even if these icons are not present on that machine.

...until you change button bar...

MVV wrote:...until you change button bar...

I know, so i said above "(as far as you didn't change the accompanying *.bar file)"

This is a good reason for not considering *.br2 file is garbage.

Irrespective of the term "garbage" which I would not apply to .BR2 files, they are cache files.
They serve the purpose of speeding up the process of displaying the buttonbar by caching the icons which are needed to display a particular buttonbar and which have been collected from different locations before.
Without the .BR2 files T.C. would be forced to collect every single icon from its original location over and over again.

The requested feature simply is to get a new option which allows to store .BR2 files in a different folder from the .BAR files., because unlike the .BAR files, .BR2 files are temporary files and (re)created automatically by T.C. if need be.

You are either [_] pro or [_]contra or [_] indifferent. And the final word will be with Christian. That's all.

Karl

karlchen wrote:And the final word will be with Christian. That's all.

Wait for him decision...

"No rustling’s heard in the garden deep"...