| View previous topic :: View next topic |
| Author |
Message |
larl473032004
Joined: 04 Jul 2004 Posts: 14
|
Posted: Thu Nov 04, 2004 9:24 pm Post subject: Custom Version Info |
|
|
Version 1.0.20 removed the AutoHotKey Branding:
"Version info (which can be seen in Explorer's file-properties dialog) is now omitted from compiled scripts. This change reflects the fact that scripts are owned by their authors and thus should have as little AutoHotkey association and branding as possible. An author can add custom version info by using a free utility such as ResHacker."
I downloaded ResHacker and tried to add Version Info, However I had no luck.
Even if I Open my.exe File with ResHacker and save it without changing anything, I receive an Illegal Operation Message.
Any help would be appreciated
Thanks In Advance |
|
| Back to top |
|
 |
Larry Guest
|
Posted: Thu Nov 04, 2004 11:49 pm Post subject: |
|
|
| You should have a .bin file in one of the folders. RESHACK that |
|
| Back to top |
|
 |
Chris Site Admin
Joined: 02 Mar 2004 Posts: 10474
|
Posted: Fri Nov 05, 2004 12:02 am Post subject: |
|
|
Sorry for the misleading entry in the changelog. I thought ResHacker could easily add a version resource, but it doesn't seem so. Even editing an existing script's version resource with ResHacker seems to damage the target EXE file (probably because it's compressed with UPX).
| Quote: | | You should have a .bin file in one of the folders. RESHACK that | I think that's the best approach. However, the bin file is currently entirely lacking a version resource. Since it's not obvious how to add one with ResHacker, I will attach a blank version resource to the bin file in the next release. That way, you can edit the bin file with ResHacker to cause all scripts you compile to have the same version info.
If anyone knows a better way, please let me know. |
|
| Back to top |
|
 |
larl473032004
Joined: 04 Jul 2004 Posts: 14
|
Posted: Fri Nov 05, 2004 1:03 pm Post subject: Custom Version Info |
|
|
| Thanks Chris |
|
| Back to top |
|
 |
Chris Site Admin
Joined: 02 Mar 2004 Posts: 10474
|
Posted: Fri Nov 05, 2004 3:39 pm Post subject: |
|
|
I've updated the installer with this change. I've tested it with ResHacker and it seems okay.
Instructions: To customize the version info of your compiled scripts, use a utility such as Resource Hacker (freeware) to edit the AutoHotkeySC.bin file. Note that ResHacker will corrupt compiled scripts, which is why only the AutoHotkeySC.bin file should be edited. |
|
| Back to top |
|
 |
ranomore
Joined: 06 Nov 2004 Posts: 178 Location: Salt Lake City, UT
|
Posted: Mon Dec 20, 2004 6:04 pm Post subject: |
|
|
The AutoHotkeySC.bin file has a bunch of icons in it. Can you list the purposes for them somewhere? Also, if I just delete a few of them, will it cause errors?
This seems like an even better way to have custom icons, especially if I all my programs use the same ones.
This also makes me wonder if an option to overwrite or keep the existing BIN file could be added to the installer. I don't know a lot about programming. Maybe it's a bad idea.  |
|
| Back to top |
|
 |
Chris Site Admin
Joined: 02 Mar 2004 Posts: 10474
|
Posted: Tue Dec 21, 2004 2:32 am Post subject: |
|
|
| ranomore wrote: | | The AutoHotkeySC.bin file has a bunch of icons in it. Can you list the purposes for them somewhere? | If you view them, they're fairly self-explanatory. There's the main try icon, and then one for pause, one for suspend, and one for pause-suspend. There is also a document-type icon. Other than that, there is a dark green H and S I believe, which are used on OSes older than WinME/XP because they look better.
| Quote: | | Also, if I just delete a few of them, will it cause errors? | I've never tried it.
| Quote: | | This seems like an even better way to have custom icons, especially if I all my programs use the same ones. | Yes, you could have a custom pause or suspend icon by substituting your own icons.
| Quote: | | This also makes me wonder if an option to overwrite or keep the existing BIN file could be added to the installer. | Since the BIN file is a verion of AutoHotkey.exe specially tailored for compiled scripts, it must be updated to cause scripts compiled in the future to have the latest fixes and features. |
|
| Back to top |
|
 |
|