$sArg1_part1 = "C:\CHDKPTP\"$sArg1_part2 = "chdkptp.exe"$sArg1_part3 = "-i"$sArg2 = ""$iArg3 = @SW_MAXIMIZE$final_arg1 = $sArg1_part1 & $sArg1_part2 & " " & $sArg1_part3Global $iProcessID = Run($final_arg1, $sArg2, $iArg3)
Lua is very fast, and allows us to extend AutoIt easily, similar to the way plugins work. This also allows us to immediately and easily utilize every package for Lua that currently runs on Windows - game engines, GUI libraries, networking, number crunching, and more.I think the biggest benefit comes from the ability to create a framework application in AutoIt, and then offload CPU intensive functions, or functions intended to be customized (plugins) to Lua.
I just started to put together an Autoit gui in order to control chdkptp.
I was, very tentatively, wondering for an interested developer - how difficult an AutoIt / chdkptp interface could be to develop?
For the benefit of those who have read this thread and wondered what the heck WinPE is :Windows Preinstallation Environment (Windows PE) 2.0 is a minimal Win32 operating system with limited services, built on the Windows .... kernel. It is used to prepare a computer for Windows installation, to copy disk images from a network file server, and to initiate Windows Setup.
Quote from: waterwingz on 06 / May / 2015, 23:31:40For the benefit of those who have read this thread and wondered what the heck WinPE is :Windows Preinstallation Environment (Windows PE) 2.0 is a minimal Win32 operating system with limited services, built on the Windows .... kernel. It is used to prepare a computer for Windows installation, to copy disk images from a network file server, and to initiate Windows Setup.That is a very OLD M$ link.M$ the current version for Windows 10 is about 5+And M$ has since changed many of the WinPE and WinRE features.I have found that it's more reliable than other Windows versions forcertain one off applications.When Windows fails WinRE will then start automatically.H-H
Continued from Post #1##:- "AutoIT" GUI, Multi-Camera Control with "PhotoScan" Example #1:- Consisting of 64 "Cheap" (i.e $US 50) Ixus 145 Cameras, as a 8x8 Camera Array, i.e 8 Cameras mounted on 8 Poles. On each of the 8 Poles the cameras are connected to a 10-Port USB-2-Hub, the 10-Port Hubs are then connected to 4x Cheap "Refurbished" 10-inch Laptops, as a pair, that are running Win-PE and a "Slave" version of AutoIT, see stuff above, the 10-inch Laptops are then connected, via ethernet cables, to a "Master-PC" that is running "PhotoScan" and the "Master AutoIT GUI" ChdkPtp will also works very well and reliably with all versions of "Win-PE". The 8x8 Camera Array can then be commanded to "Shoot" via AutoIT, ChdkPtp and the USB-2 Hubs as an 4x16 Camera Array this minimises the "Shoot" Delay between the 64 Cameras in the array. This is the simplest method of "Shooting", but the cost is the camera "Shoot" delay.
I don't really understand why you want to involve autoit at all. If you want a GUI, learning enough IUP and Lua to customize the chdkptp GUI would seem like a better approach.
(iv) I couldn't start to imagine how to use IUP to control multiple instances of chdkptp
I can't, currently, think that IUP will provide any more functionality than AutoIt
Started by DBgit
« 1 2 »
Started by gkguru
« 1 2 »
General Help and Assistance on using CHDK stable releases
Started by Dirk
Started by oneaty
« 1 2 »
Completed and Working Scripts
Started by bugbear