Closed evaldask closed 7 years ago
This seems reasonable, but I'm concerned that it will break anyone with a pre-existing configuration using the old parameter names. What do you think is the best way to proceed here?
I see two ways of doing it:
What do you think about it?
The biggest issue is that the master
branch is released to all distros, so there's no way to not change the behaviour on Indigo, short of just not making any more indigo releases, or creating an indigo
branch at this juncture, and allowing the breaking change to go into master
, targeting Jade and Kinetic.
Check out pull request #91 -- I've added a hard option to strobe on GPIO2. It's not as classy as this, but it keeps backwards compatibility. It'd be nice to be able to set whichever GPIOs, but GPIO1 and GPIO2 are the only ones that PointGrey recommends in their literature anyways.
If we use the FlyCapture software as a reference, then I'm inclined to suggest that we go with #91. It makes sense to me to make the dynamic reconfigure parameters mimic the FlyCapture demo software as closely as possible to
What do you think?
Closed in favour of #91. Thanks!
Instead of having hardcoded GPIO pin number for strobe added same options as triggers.