Gerald wrote:
Not that it matters much, since fractint's autokey feature doesn't seem to be used by many:
Actually, it's an invaluable feature that can be used for many purposes like demos and debugging.
When playing an autokey file that was created for version 19.x and earlier, panning the zoom box now moves it too far, resulting in a much different image than was intended.
Understand that the autokey feature works by directly trapping user interface keystrokes. If the user interface changes, old autokey filews won't necessarily work. There are things the developers can do to minimize this, by adding new menu items to the bottom of menus, etc. It is desireably to not make changes that would break compatability with old autokey files. But fundamentally autokey files are designed to work with the version that created them. If autokey files were procedural instead of just trapping keystrokes, the situatrion would be different. That would be better, but would require a big redesign. We do need to check to make sure that the new virtual screen logic uses the standard fractint keyboard input routine. Tim
This can be checked using demo.bat, demo.par and basic.key from the autokey files created for version 19.x and still part of the fractint distribution, choosing "Basic commands demo". (Not to forget: One has to change line 25 in basic.key from "DOWN * 2" to "DOWN * 4" to adapt it to the additional two prompts on the <x> screen introduced in, I think, fractint 20.1.)
Regards, Gerald
_______________________________________________ Fractdev mailing list Fractdev@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractdev