-
Notifications
You must be signed in to change notification settings - Fork 4
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
Allowing Base64Encoded Images #4
Comments
Unfortunately, this would be a bit of a pain in the ass to do. At the moment images are loaded by windows using node-not-the-systray/src/icon-object.cc Lines 19 to 20 in ec563fc
So I can't really control how it loads from a path, using that. To do this properly, I could add an implementation using something like That said, for this purpose you may instead load from a windows resource of the current executable, using |
Ahh ok thanks for the info, i do already have a workflow for changing the default icon for the executable using resource hacker would the id i set the icon be the same i use for the resource_id if i was using rcedit as well? If so i will definitely use that way instead as it will save me a bunch of time. |
Yep, though it looks like only number ids are supported at the moment, sorry! |
Note that |
One more thing, IIRC, it would be the id of the ICONGROUP resource, not the individual ICON. |
Awesome yeah i was about to ask that when going through all the ids i currently see when just opening the exe in resource hacker ill def test it later today and see if it works out |
Absolutely perfect! Worked like a charm and you are indeed correct it is the icongroup id. |
Glad it worked out! |
when packaging with pkg the module cannot find the image in the virtual snapshot path and being able to use a base64Encoded string for the image would help that issue if possible.
The text was updated successfully, but these errors were encountered: