Sign In
Create Account
Last active: Jul 31 2015 01:53 PM(Content in this thread stored within ahk.net will not display correctly if that domain is experiencing difficulty)
Download: ahk.net HKC_65.14b.7z
Download: mediafire HKC_65.14b.7z
Recent Update Information
> Fix - Duplicate icons when preserving all resources <
When adding an icon resource with the same resource index as an icon within the interpreter, HkC should have removed all other icons in that index before adding your icon, but it did not. This bug has only been fixed because I tore out the whole chunk of code for handling this and used a temporary fix from a previous build of HkC. Until further notice If the "Keep original resources" option is enabled and you set the main application icon or add an icon via resource configuration, all other default interpreter icon resources will be removed.> New - List Import button for each configuration tab <
The resources, execute, version info and patches interface tabs have a button added that invokes an import popup menu. This menu allows you to browse or select from a list of templates (.hkc files) found in the HKC subdirectory and looks identical to the template menu invoked via the input button or the large icon. The difference being that files selected via this menu will load only the grouped configuration options within that are related to the dialog list tab in which the menu is invoked. Settings imported this way will be added after any that currently exist within the active list, duplicates will still be parsed out. Just so that you know this works exactly the same as if you drag and drop a config file onto the dialog list field.> New - Import resource list from interpreter <
The previously mentioned list import button menu for the resources tab has an option to populate the dialog list with entrances that are already found within the interpreter. The detection of this file is identical to that which happens during the build operation. It is still very early days on this and would appreciate any ideas users might have regarding this functionality. It currently does not handle properly: Custom resource type entrances as string Resource names as string entrances Additional information It is pointless to allow the modification of the RT_ICON resource entrances so they are actively parsed out of the list, only the RT_GROUPICON entrances remain. It is also fairly useless keeping the generated RT_VERSION entry because this should be handled by HkC, although it is not parsed out of the list, and keeping it intentionaly prevents HkC adding any version information defined via the version info tab/cfg. After using this feature you will notice in the list that the file fields are not filled for any entrances (obviously). Remember that when a file is not defined for a resource instruction during build, HkC will attempt to delete that particular resource.> MISC <
Incorrect information from the crossover from AutoIt3Camo to
HotkeyCamo was found in many of the rtf help documents, while very
minor they could have easily confused a new user.
The following template examples were wrong due to the @OUT> macro
being used instead of the @BIN> macro:
Packing {MPRESS}.hkc
Packing {UPX}.hkc
Plus the following Execute tab elements were wrong for the same
reason:
UPX --best
UPX --compress-icons 0
MPRESS -s
Older Update Information
> Fix - HkC to Ahk2Exe version information injection bug <
Tried to be cute with this pointless functionality by adding the output executable version information instead of HkC's version. This was also likely to be the cause of the corrupt/unrecognized first line interpreter error message that occured sometimes. Although steps have also been taken to ensure this particular bug [u]should[/u] not resurface.> Change - Default setting to delete interpreter resources <
The file USR.pref.def (Created as USR.pref by HkC) is distributed with the option HKC_KOR set to 1 which turns the default behaviour of keep original resources to on (instead of off) for new users. Existing users simply change the above within USR.pref Remember these default settings within [i]USR.pref[/i] only occur when opening a config file that does not already have the options that have a value.
> Fix - Corruption when preserving xml manifest <
The cause was a simple Ahk version string patch which has now been removed
> Fix - Import old HkC config options (menu item) <
Check for uneccesary dependency resulting in error message.
> New - Packer support method <
For AutoHotkey basic only, a more robust method of using software
armoring tools on your output exe has been implemented through
the execute 'Run' config parameter by using the 'During Build'
option.
This is an extension of the old method HkC used to use by patching
the default upx string within the compiler, which was at best very
twitchy.
This time the compiler executes HotkeyCamo and not the packer direct
So we gain the following benefits:
A) More than one program can be executed 'During Build'
B) The commandline length is not restricted to the upx string length
C) Entrances identical to normal execution which provides a bit more
control over the program such as:
* visibility
* Explicit program path
* working directory
Things to note from this method:
A) During build execution heritage
HkC.exe
Compiler.exe
HkC.exe
Desired Program.exe
...
Look at either of the following to get a greater understanding:
A) The packer menu elements in the Execute tab.
B) The packing example templates from the menu invoked by clicking
on the 'Input' button in the main tab or the large interface icon> Fix - Resource handling for Ansi bin files <
Something that has always bothered me concerning resource string types and or string id's was the loss of the last character in the string thanks to the Ansi resource update api.> New - Ansi or Unicode bin file resource handling <
The build config option HKC_BRM can be used with either ANS or UNI as a parameter. (Default is Ansi)
> Info - Newer builds of AutoHotkey (L/H/2) <
Entirely untested but such builds that do not use the exearc header will probably work just they won't be protected. (don't blame me) Other than that all other elements of HotkeyCamo should work with them. (Assuming that the Ahk2Exe commandline has not changed) Couple of things to note if you are trying to use HkC with them: When packing just use 'Post build' as the run parameter. Completely ignore 'During build'. You will need to specify the names/paths to the compiler and the interpreter since they will likely not be named or located the same as the Ahk basic files.
> Fixes <
Numerous other little things that caused me to facepalm till I bled :/ Oh and the examples have been modified to go along with recent fixes, check em out if in doubt.
Vlad
Back to top
