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.
Don't feel guilty about asking, just don't expect me to do it
I'm happy to get feature requests and bug reports, but please understand many of them will just be filed away to be addressed at some time in the future.
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?
The dcimdl snippet I wrote may evolve into something useful I'll include in the distribution, though I mostly did it to try to illustrate how you can solve this kind of problem for yourself in the future.
When you say something like
To test that I do need the single call that does everything (ie shoot & transfer) and it does not have to be elegant or generic // it just has to work.
I'm likely to say "well then, go write it yourself"...
Same goes for fudging the real vs market ISO stuff. If I come up with a generic way that is accurate across all the cameras, then I'll add it (time permitting). If it requires each user generating a spreadsheet and entering it in the code, I probably will not.
In these situations, I will try give you the information you need to write your own one-off hack, but that won't extend to writing/testing every line of code.
I hope ... do these requests (shoot, transfer, clean up chdkptp GUI, etc) not fit in??
Sure, most of these things would be good to do eventually. The GUI in particular has grown out of some proof of concept code I threw together to develop the live view protocol. I have some ideas about how it should be re-designed, but that will take time. I label current chdkptp builds as "alpha" or even "pre-alpha" because it really is unfinished. I try to keep the existing functionality usable, but there's a lot to do.
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.
I certainly wouldn't write these for you, but again, chdkptp is designed to be extensible. I recognize that a lot of people who want remote control capability want it for unique applications, the idea is that it should serve as a framework each user can customize if they are willing and able to do so.
