Increase internal associations count
Moderators: white, Hacker, petermad, Stefan2
Increase internal associations count
It seems to be capped at 250.
Can't add more (no visible error, just a sound) using the gui, and manually increasing the number to 251 in the config doesn't seem to work either.
Also it would be nice to just change the icon for a certain file extension.
For example image formats (jpg, gif, png):
I'd like them to open with the same tool (irfan view)
So i would make one internal association for:
*.jpg; *.png; *.gif
..and associate them accordingly.
But i still would like to have a different icon for each of them.
The way it is now i have to make one entry for every extension. But let's say i want to add another program or change the default. Now i have to change them all individually again.
Can't add more (no visible error, just a sound) using the gui, and manually increasing the number to 251 in the config doesn't seem to work either.
Also it would be nice to just change the icon for a certain file extension.
For example image formats (jpg, gif, png):
I'd like them to open with the same tool (irfan view)
So i would make one internal association for:
*.jpg; *.png; *.gif
..and associate them accordingly.
But i still would like to have a different icon for each of them.
The way it is now i have to make one entry for every extension. But let's say i want to add another program or change the default. Now i have to change them all individually again.
Ini file 64k limit per file or per section?
Isn't that is a 64K limit per section 'only'.
But then I have a few re directions too:
64k is huge (for TC settings), my whole ini is 25k only.History.txt wrote:23.04.06 Added: The Ctrl+D menu now supports up to 998 items (if the limit of 64k per ini file section isn't reached before)
But then I have a few re directions too:
[left]
RedirectSection=WIN_Tmp.INI
[right]
RedirectSection=WIN_Tmp.INI
i'm using redirect too:
wincmd_associations.ini is 56,5KB (951 lines)
from Filter1 to Filter249.
Filter34=*.avi for example has 9 other entries for various tools like vlc/mpc/mediainfo/...
Code: Select all
wincmd.ini
[Configuration]
UseIniInProgramDir=7
RedirectSection=%COMMANDER_PATH%\profile\wincmd_config.ini
[Associations]
RedirectSection=%COMMANDER_PATH%\profile\wincmd_associations.ini
from Filter1 to Filter249.
Filter34=*.avi for example has 9 other entries for various tools like vlc/mpc/mediainfo/...
2MVV
i used to do this too - in 2008
i even made a post back then asking for internal associations as a feature:
http://www.ghisler.ch/board/viewtopic.php?p=146549
i used to do this too - in 2008
i even made a post back then asking for internal associations as a feature:
http://www.ghisler.ch/board/viewtopic.php?p=146549
I support the idea of individual icons per filetype in internal associations. It could work like this.
FilterX.icon=PATH_TO_FILTER_X_ICON
works as the default icon for all icons covered by this association. On top of this logic let the user define filetype-specific icons. Something like:
FilterX.icon.bmp=PATH_TO_BMP_ICON or even
FilterX.icon.jp*g=PATH_TO_JPEG_ICON
FilterX.icon=PATH_TO_FILTER_X_ICON
works as the default icon for all icons covered by this association. On top of this logic let the user define filetype-specific icons. Something like:
FilterX.icon.bmp=PATH_TO_BMP_ICON or even
FilterX.icon.jp*g=PATH_TO_JPEG_ICON
It is a real problem when you want to have some common settings for a group of extensions but also for some different setting for each of them, e.g. same context menu entries but different icons. Icon-only association could be relatively compact. But currently you can't apply multiple IA sections for one file, you have to repeat contents of large IA section for every matched file type.
Merging or intersection of filters was mentioned many times (e.g. 1, 2, 3) and it could help in such cases: one association only defines context menu entries for all extensions, but it is not used exclusively, it is merged with another one that defines an icon for some extension.
Merging or intersection of filters was mentioned many times (e.g. 1, 2, 3) and it could help in such cases: one association only defines context menu entries for all extensions, but it is not used exclusively, it is merged with another one that defines an icon for some extension.