TIP: Batch processing examples and AutoHotkey

[shaswin]

See some batch files (.bat) examples for batch processing in the ZIP attachment. Using the command CHCP in the batch makes it possible to use other extended characters (different code page in MSDOS COMMAND application) as standard till the .bat/.cmd file is finished, so letters like ë, ä, ï, etc. in the FILENAME/FILEPATH will be allowed/recognised in the Ple4Win batch processing.

Also the AutoHotkey v1.1.37.02 source code script examples for making Ple4Win Professional in- and output is also attached as a ZIP-file. The scripts needs to be changed and is not valid anymore (outdated, because the User Interface (GUI) of Ple4Win Professional v4.8.1 has changed). The scripts are compatibel with the GUI of Ple4Win Professional v4.7.0. I am not updating the source code of the scripts anymore. Nowadays a new version of AutoHotkey v2.0.19 (Quick Reference | AutoHotkey v2) is available and so, the source code needs to be converted slightly here and there or you can still use AutoHotkey v1.1.37.02 (Quick Reference | AutoHotkey v1) for compiling. If you don't have the Export Communication Ple4Win module (E0) you can use a virtual printer i.e. ImagePrinter Pro v6.3, where the licence is very cheap. In the AHK (AutoHotkey) script for Ple4Win output we used the ImagePrinter Pro multi-page printing as PNG-file(s) and then importing all PNG-files with titles and a main index in a Word output file through a VBA macro.

Using AutoHotkey for the Ple4Win Educational version for making it a part of an automated computing chain is forbidden by EDS.
Using VBA macros in Excel and Word can automate a lot of things with automating reports to PDFs.

So, this information is made available as example for how to make a good automated batch computing chain for the Ple4Win Professional version (multiple) project(s).

[B Bharatadjaya MSc]

Hey Shaswin,

Thanks for the tip.
This tip has been added to our ticketing system (2879).

Regards,
Billy

[Dr. J Foerster]

Again, thank you for this information.

Please note that using scripting tools such as AutoHotKey is forbidden for both the educational and the professional version of the program, see the General Terms and Conditions
 (link to document at the end of the page), especially paragraph 5.3 (xi)

[shaswin]

Again, thank you for this information.

Please note that using scripting tools such as AutoHotKey is forbidden for both the educational and the professional version of the program, see the General Terms and Conditions
 (link to document at the end of the page), especially paragraph 5.3 (xi)

Jens, the scripting in AutoHotkey is NOT hacking, it simulates the mouse clicks and keyboard (hot)keys strokes, where a human is not (always) needed anymore to type with a keyboard or to scroll/click with the mouse (a human can take a break for a coffee  or have a discussion with a colleague) and it increases the productivity of the engineer a lot. I did once almost 8000 different PLE configurations calculation in 48 hours without any interaction with the PLE-program and the PLE-computer before the Gereral Terms And Condtions was written with a different script then above. I only monitored it through VPN with a laptop at home if it stopped at office or some error happened, but it didn't stop the calculations and all errors had been mitigated before with the script. It created also PDF reports. If AutoHotkey is forbidden then a mouse and keyboard should also be forbidden, I think  .

During the scripting with AutoHotkey for years together with my former collegues I tracked a lot of bugs in Ple4Win, which i informed you guys on the forums and e-mails. Mostly got fixed. So, it was good for everyone, because PLE is a very stable now and less unhandled program errors now.

I want to share this information, so the productivity of the PLE engineers can be increased/improved.