You also could have explicitly informed users in your readmes and given users an option regarding the said reasoning:AkulaBig wrote: 2023-05-24, 17:59 UTC ...I ask you to replace the i_view32.ini or i_view 64.ini file with files from the plugin. For my plugin, it is necessary that there is an option in i_view32.ini or i_view64.ini
[Extensions]
CustomExtensions=ACR|ANI|ARW|AWD|B3D|BMP|CAM|CDR|CIN|CLP|CR2|CR3|CRW|CUR|DCM|DCR|DDS|DCX|DIB|DJVU|DNG|DPX|ECW|EMF|ERF|EXR|FIT|FITS|FPX|G3|GIF|HDP|HEIC|ICO|ICS|IFF|IMA|IMG|IW44|J2K|JFIF|JPC|JP2|JPE|JPEG|JPF|JPG|JPM|JLS|JNG|JXL|JXR|KDC|LBM|MNG|MOS|MPO|MRC|MRW|MSK|NEF|NRW|ORF|QOI|PBM|PCD|PCX|PDN|PEF|PGM|PNG|PPM|PSD|PSB|PSP|RAF|RAS|RAW|RGB|RLE|RW2|RWL|SFF|SFW|SGI|SID|SRF|SRW|SUN|SVG|TIF|TIFF|TGA|WAD|WAL|WB1|WBC|WBZ|WBMP|WDP|WEBP|WMF|WPG|WSQ|X3F|XBM|XCF|XPM|XR|
Otherwise, if an unfamiliar extension is detected, IrfanView will display an error window...
{1} replace the i_view32.ini or i_view 64.ini file with files from the plugin [as it is so far].
{2} update users' i_view32.ini/i_view 64.ini [Extensions] section taking its content from the plugin's i_view32.ini/i_view 64.ini and allowing to keep the rest of user-specific settings intact.
OK, at least now it's clear why the requirement exists.
Thanks.