why 256x256 icon not showing in Gui ?
I too had some issues with this in the past.
Some possible reasons for this are:
1 - The icon in question holds more than 1 image (this is very common with icon files), and the 16x16 (with low quality) image is the one being chosen for display -> If this is the case, i suggest you download an icon editing tool and remove all undesired images from the .ico file.
2 - The icon is being automatically resized to fit some smaller display frame and this resizing is blurring the image to low quality -> If this is the case, and if that icon is a really nice one, i suggest that you try to edit and convert the images to a lower size (compatible with the display frame) manually, so you can keep a keen eye on the quality. Otherwise, if the icon is unimportant, just download a bunch of cool icons and test each of them till one "fits" the display frames (this is what i did, lol ).
3 - The compiler is causing this "distortion" of the images when it merges the icons into the executable -> if this is the case, either change the compiler or reverse engineer the resource section of the output PE.
Best wishes :wink:
"What is a suitable automation? Whatever saves your day for the greater matters."
Barcoder - Create QR Codes and other Barcodes using only Autohotkey !!
I'm using Articons pro tool, Icon is clean ... only bmp or png file can embed safely in Gui .. I did not understand that , still not solved :lol:
Improvements to Icon Support
Icon resources of any size supported by the operating system may be extracted from executable files. When multiple sized icon resources exist within an icon group, the most appropriate size is used. Prior to revision 17, an arbitrary icon resource was selected by the system, scaled to the system large icon size, then scaled back to the requested size.
Source: AutoHotkey_L New Features
Gui Add, Picture, w256 h256 Icon1, test.dll Gui Showtest.dll contains one icon with two images: one 16x16 "A" and one 256x256 "B".
Running the script on AutoHotkey v1.0 produces A scaled up to 256x256.
Running the script on AutoHotkey_L produces B at its original size, 256x256.
h256produces B at 256x256 on AutoHotkey_L and A at 256x16 on AutoHotkey v1.0.
w256 h256produces A on either version, but on AutoHotkey v1.0 it is scaled up to 32x32.
Huh? AutoHotkey_L does not mean "AutoHotkey library version".