Button bar in TC running from USB

[roentgen]

When running TC from USB stick and the drive letter changes, the icons in the button bar are extracted again. This means that for the first start I have to wait for ~30 secs until TC becomes responsive.

This is odd especially because I use variables in button definition. Like:

Code: Select all

button19=%COMMANDER_DRIVE%\Programs\IrfanView\i_view32.exe,1
cmd19=""%COMMANDER_DRIVE%\Programs\IrfanView\i_view32.exe""
menu19=IrfanView

If I am to take a wild guess this is because of the data that gets stored inside the .br files that maybe is using absolute paths. Whatever the reason is I would really like to have this fixed

[m^2]

When running TC from USB stick and the drive letter changes, the icons in the button bar are extracted again. This means that for the first start I have to wait for ~30 secs until TC becomes responsive.

This is odd especially because I use variables in button definition. Like:

Code: Select all

button19=%COMMANDER_DRIVE%\Programs\IrfanView\i_view32.exe,1
cmd19=""%COMMANDER_DRIVE%\Programs\IrfanView\i_view32.exe""
menu19=IrfanView

If I am to take a wild guess this is because of the data that gets stored inside the .br files that maybe is using absolute paths. Whatever the reason is I would really like to have this fixed

I can't confirm this.

[ghisler(Author)]

Is this really on the same PC? TC should re-read the bar only if either
- the .bar file has changed, or
- the screen color depth has changed (e.g. 16 bit vs 32 bit colors)
- the configured icon size has changed
- options: with/without frame, small icons, xp style bar

If none of these have changed, then the checksum is the same as stored in the .br2 file, and the bar will not be recreated.

[roentgen]

No, it isn't on the same PC.

I guess that

the screen color depth has changed (e.g. 16 bit vs 32 bit colors)

must be the most plausible reason.

Tough luck...