Abd to add to that, it seems that most of the functions will be the same. From what I've read, it seems that the main changes will be a new numbering system.
Not really correct.... v4 will still support v3 style scripts, and OEM codes, but in a legacy mode. Continued use of v3 scripts will be discouraged, as the v3 mode will, at some point, be phased out. The hope is, everyone will see how much better the v4 mode is, that they will, over time, move completely over to v4. In any case, v3 development will stop, while v4 will continue to improve and evolve.
The new v4 VB interface and OEM codes are *completely* different, and VASTLY improved. The VB function naming is far clearer, and FAR more consistent. The VB interface and OEM codes will be documented, and explained in detail. A VB include file will be provided with clear names for the OEM codes (you can still use the numbers if you prefer, though I don't know why you would...). There are a LOT of nice new functions providing capabilities that do not exist in v3. Overall, v4 will be MUCH easier to learn, MUCH easier to use, and MUCH better documented and tested. Macros will be easier to write, easier to debug, and require fewer lines of code than for v3.
For screen editors, as far as I'm concerned the only one to use is MachScreen. It is very stable, very easy to use, and is constantly being updated. It's just added the capability to import pages from another screenset file, which will make it possible for an OEM to provide a screenset file containing add-on pages to support their hardware or software that the user can add to his favorite screenset very easily.
Regards,
Ray L.