After further dicussion: The attached patch makes a number of changes to gearchange.comp.
The main change is that the number of gears is now set by a num_gears modparam rather than "personality". This has allowed me to get rather carried away and the component is now a bit polymorphic. With a num_gears modparam it creates a scale and select for each gear. It also creates a pin to indicate which gear is in use. Without the modparam it behaves like the old version, with a single "sel" pin to swap between gears 1 and 2, and a "reverse" pin to indicate that gear 2 runs backwards. In this mode it does not have numerical gear input or output pins. Talking to Seb, he opined that this was all a bit too elaorate, and having a component with two behaviours and one name is silly and confusing. I tend to agree. So, should we use this version, which tries to be all things to all men, or would it be better to drop the compatibility mode and break any existing configs (of which there are probably rather few which use it) -- atp "Torque wrenches are for the obedience of fools and the guidance of wise men"
gearchange_2.mbox
Description: Binary data
------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
