-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make buttons toolbar custom hot images more robust #546
Comments
Here the fcb file: |
Hi, The default icons have never had hot versions, perhaps you had custom ones before? I am seeing a couple of problems with custom hot images though:
However, those were both problems in 1.7.0 as far as I can see. If you're seeing a difference from 1.7.0 could you compare with a portable installation? Thanks |
Added pngs of light oxygen set with size 20x20 pixel as hot image. Looks good on hover. |
That's good – are you seeing a regression from 1.7.0, then? (I need to improve the general logic around custom images in any case.) |
As far as I can see, there is no regression. In Version 1.7.0, I have used custom images for both normal and hot: 22x22 px pngs. The normal svg buttons in 2.0.0 alpha 1 are awesome, so I use them. The 22x22 px png for hot are too big and are cut, so I resized to 20x20 px. Please enable svg support for custom images. It seems, that Windows Imaging Component (WIC) doesn't support ico. You can drop it from the format list. |
OK – I'll repurpose this issue for fixing ICO files and making things a bit more graceful when hot images are the wrong size.
Thanks!
There's no native SVG support at the moment, I'm afraid (the SVGs for the default icons are converted to ICO files first). SVG support could be added using a library, though it would make more sense following #421.
ICO and BMP files aren't (meant to be) loaded through WIC there – ICO seems fine for non-hot images so not sure what's going wrong for hot ones, but I'll fix it. |
The Default Button Hot Image isn't working anymore.
The text was updated successfully, but these errors were encountered: