Just a note for "Companion_xx". To represent the relationships between JPG/TIFF/ORF/CR2 I have to use 30 entries in XnView:
Code: Select all
Companion_00=jpg:tiff
Companion_01=tiff:jpg
Companion_02=jpeg:tiff
Companion_03=tiff:jpeg
Companion_04=jpg:tif
Companion_05=tif:jpg
Companion_06=jpeg:tif
Companion_07=tif:jpeg
Companion_08=cr2:jpg
Companion_09=jpg:cr2
Companion_10=cr2:jpeg
Companion_11=jpeg:cr2
Companion_12=orf:jpg
Companion_13=jpg:orf
Companion_14=orf:jpeg
Companion_15=jpeg:orf
Companion_16=cr2:tiff
Companion_17=tiff:cr2
Companion_18=cr2:jpeg
Companion_19=jpeg:cr2
Companion_20=orf:tiff
Companion_21=tiff:orf
Companion_22=cr2:tif
Companion_23=tif:cr2
Companion_24=cr2:jpeg
Companion_25=jpeg:cr2
Companion_26=orf:tif
Companion_27=tif:orf
Companion_28=orf:jpeg
Companion_29=jpeg:orf
Apparantly the reason for the inflationary application of "Companion_xx" is that "JPEG"/"JPG" and "TIFF"/"TIF" are separate extensions. Also the declaration is only one-way. Suggestions:
- use "::" instead of ":" to indicate bidirectional binding
- use ";" to separate multiple extensions
For example:
could replace 8 definitions:
Code: Select all
Companion_00=jpg:tiff
Companion_01=tiff:jpg
Companion_02=jpeg:tiff
Companion_03=tiff:jpeg
Companion_04=jpg:tif
Companion_05=tif:jpg
Companion_06=jpeg:tif
Companion_07=tif:jpeg
Another problem is that XnViewMP 0.39 seems not so supprt "Companion_xx".
This might by natural, however, since its ini-file not even has a "[File]" section.
