(Does anyone see a simpler way to test for both variables in this loop without adding that extra if j then wend line? As that would add an extra 10ms lag when not using the "Fast Shoot" option.)
Hmm... good plan. But why do I suspect that the longer a script is, the longer it will take to run? In the "old days", all BASIC programs had to be parsed from the beginning up to the loop or function needed each time it had to test for a new condition. So while even though the loop in use at the time might be smaller and run faster for that particular function, it takes longer for the software to run through the whole thing to find that loop each time. Granted, this isn't hitting the 10ms per line speed-limit, but the uBASIC speed itself, yes? No?But then, come to think of it, once (or if) the internal shoot command becomes faster, then this will be done away with and whatever fastest method found will have a script just for that purpose.
My mind is still thinking from the old 6502 1mHz processor days, where every line mattered.
Started by solarflare « 1 2 3 4 5 » General Help and Assistance on using CHDK stable releases
Started by billgwells General Help and Assistance on using CHDK stable releases
Started by fvdk Creative Uses of CHDK
Started by georg2011 Script Writing
Started by TMHKR « 1 2 3 » General Help and Assistance on using CHDK stable releases
