@waterwingz
You always come through with right thing at the right moment, so this sure helped. Trying to edit noobie lua code in Notepad is quite a chore. I found this editor in link you provided:
http://luaedit.luaforge.net/... which at least colorizes the reserved words. For example, I just loaded in cli.lua and functionality jumped right out of the screen at me // nice // first chasm leaped over, thanks.
@reyalp
Quote "concatenation
http://www.lua.org/manual/5.1/manual.html#2.5.4"
That's what I read at first and was no better off // examples I found are very poor in the manual. What actually helped though was your code because now I can translate the code reality back into the abstract requirements giving me the a reasonable starting point to work the normal direction.
Quote "Some future version might, but I work on it in my limited spare time, so there's no schedule. You should be able to do what you want with some additional programming"
That, is very comforting to know. Ideally, you would not use the SD card as a file buffer. How you'd transparently transfer the Canon files I think would be a major challenge w/o Canon writing to disk. For example the S90 has both JPEG and Canon compressed CR2 (7MB instead of 16MB CHDK) for significantly faster direct transfer. For now I will assemble a crude single call with what you've provided so I can execute the next series of acceptance tests, which has top priority ... because I don't know yet if everything will work properly in the instrumentation environment.
Quote "If that is not something you are prepared to do, then chdk and chdkptp may not be the right solution for you."
I recall mentioning some time ago your solution had great potential for my project. I can say now it has even greater potential ... I'm still around for very good reasons ... so ... I am proposing we take advantage of each others' different expertise areas for mutual benefit.
Quote "I'm not interested in writing one-off hacks just to move your project forward."
Mmm .. that hurts // I feel even more guilty for asking functionality from you so I will try to express what I've explored earlier in another way. Would you consider the piece you wrote a one-off hack exclusively for me and not something you could have basically ready to implement in a future version you talk about, or even include it in your standard distribution for folks to use right away? That is something honestly I am uncertain about. Perhaps it is the case. I present my feature requests within the context of the community and my perception of standard functionality, I hope ... do these requests (shoot, transfer, clean up chdkptp GUI, etc) not fit in?? Perhaps there is an eyes-of-the-beholder discrepancy between us. To illustrate the difference, here is one explicit example of what I consider I am not permitted to request of you. The spectrometric aperture is in the dead center of the visual field. Whenever I do a modification to the instrument, or just from aging, it has to go through realignment. It's a horrendous job, requiring shooting images, putting them into an editor, finding the aperture location and iterating the alignment settings. It can easily take a whole day. Do you see where I'm going? ... a reticle crosshair with a circle target in the center of the liveview with a user-defined size, black, white, XOR, with crosshair size settable independently of circle diameter // pushon // pushoff // and my instrument would be realigned in under an hour. That to me would be a personal request.
So as much as I'd love to have it especially that CHDKPTP is giving me a precision 640x480 liveview, the reality is I cannot ask for it. Do you see my point?
