v2 Feature Request - User-Defined Control Surface Count
Posted: Sat Mar 01, 2014 3:38 pmMarc,
While you're banging around those pots and pans in the D8Bridge kitchen, perhaps you'd consider another tasty ingredient for v2? If v2.x could enable users to specify the number of control surfaces rather than being limited to 3 as in v1.1, one invocation of D8Bridge could manage the totality of surfaces. For example, 2 or more d8bs could be operated under 1 D8Bridge instance rather than multiple instances. No resource contention or confusion between D8Bridge instances. Track shifts would shift across the total track count contiguously. The control surface count could be managed through the config file. A configuration of 2 d8bs could look like 1 MCU + 5 XTs to D8Bridge. I wouldn't want this to slow you down any on v2.0; I imagine this is not a priority for many D8Bridge users. But if it could be baked into the v2 code base for later implementation in v2.1, v2.2, that would be cool. Just a thought. Thanks!
While you're banging around those pots and pans in the D8Bridge kitchen, perhaps you'd consider another tasty ingredient for v2? If v2.x could enable users to specify the number of control surfaces rather than being limited to 3 as in v1.1, one invocation of D8Bridge could manage the totality of surfaces. For example, 2 or more d8bs could be operated under 1 D8Bridge instance rather than multiple instances. No resource contention or confusion between D8Bridge instances. Track shifts would shift across the total track count contiguously. The control surface count could be managed through the config file. A configuration of 2 d8bs could look like 1 MCU + 5 XTs to D8Bridge. I wouldn't want this to slow you down any on v2.0; I imagine this is not a priority for many D8Bridge users. But if it could be baked into the v2 code base for later implementation in v2.1, v2.2, that would be cool. Just a thought. Thanks!
