On Tue, Aug 31, 2010 at 2:32 PM, Blaise Gassend <
blaise@willowgarage.com> wrote:
> Hi Jack,
>
>> For the next release (Diamondback) removing the reset entirely might
>> be worth trying, but I'd hate to make a change like that in the
>> current (C-turtle) release, since it might break other users whose
>> cameras were working already. I'll look into this further, and
>> experiment with the cameras available here for regression testing.
>
> This might be worth adding an parameter for, as there are probably
> cameras out there that won't work well without the reset. If the
> default setting is to do the reset then you won't break anything that
> is currently working.
Good idea.
> While this is, strictly speaking, an API change, people who would use
> the added parameter cannot currently use the driver. Hence I think we
> can argue that this is a bugfix and push it into cturtle.
One could argue that API *extensions* that are (1) backwards
compatible and (2) needed to fix a bug are legitimate for maintenance.
There may be more cameras that don't tolerate resets. A general
C-turtle fix would help. Diamondback is far in the future.
--
joq
(text/plain)