Tony wrote:
There doesn't seem to be that much actual documentation even in the > Fractint manual about how to actually use the autokey script feature. I'd really like to have a definitive "primer" of the proper "language" and syntax" that can be used in an autokey script file. I have also attached a copy of one of my autokey script files as an example.
It's basically literal keystrokes as you would type them in , with some special words for special keys. Have you found the section on autokey in the docs? You have to search a bit, it's under startup parameters. If you can't find it, I could upload it in a message.
I was hoping that one could "call" autokey script files by using the "G" command and thus have "nested" processing of multiple script files. I have tried to access other features via the "G" command and I'd really like to have a definiteve "primer" of what can be done via the "G" command.
Basically, the "G" command lets you type in (almost) anything interactively that you can type in on the fractint command line. I say almost because I'm sure there are some limitations. For example: passes=2 changes the passes mode from whatever it was (guessing is the default) to 2. The results is the same as if you started fractint with: fractint passes=2
I have been unable to load autokey files via the "G" command either manually or from a autokey script file.
The autokey feature only works when it is started at runup. This is probably hard to change. If making an "include" command within an autokey file would suit your needs, it might not be too hard. The problem, though, is since the autokey commands are literal keystrokes, their effect depends on fractint's state. So you can't just include any old key file inside another without paying attention to whether the keystrokes make sense with fractint in the state it's in when the file is included. Sorry that thought is so convoluted :-)
I was wondering which features can actually be controled via the "G" command?
I'll look in the code and give you a list.
If you are thinking of upgrading Fractint's autokey script language, you have my vote. I definitely think an internal script language for Fractint with just a little bit more muscle than it now has would be a most useful feature.
I have "thought" about it in the past :-). These days, though, the big topic is porting fractint more than adding new features. It would make a lot more sense to implement a macro language after the program is ported. Tim