This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
roadmap:directed_choke [2019/02/11 11:00] – deva | roadmap:directed_choke [2019/03/17 09:34] (current) – [Proposal 3] deva | ||
---|---|---|---|
Line 11: | Line 11: | ||
Ride and RideBell should not choke each other but RideGrab should choke both Ride and RideBell. | Ride and RideBell should not choke each other but RideGrab should choke both Ride and RideBell. | ||
+ | |||
+ | The implementation in the engine is rather straight forward so this is not described here. | ||
IRC discussions with HJ about this feature: | IRC discussions with HJ about this feature: | ||
Line 18: | Line 20: | ||
=====XML proposal===== | =====XML proposal===== | ||
- | Like the current instrument group feature the directed choke should be expressed | + | Like the current instrument group feature the directed choke should be expressed |
====Proposal 1==== | ====Proposal 1==== | ||
Line 59: | Line 61: | ||
====Proposal 3==== | ====Proposal 3==== | ||
- | Add a chokelist xml tag containing the list. This approach is more like what would be expected in XML but (in my opinion) looks rather ugly. | + | Add a chokelist xml tag containing the list. This approach is more like what would be expected in XML but (in my opinion) looks rather ugly. This approach may however make it possible to add more control to the choking, like for example setting the ramp-down time or curve pr. choke which may be useful. |
<code xml> | <code xml> | ||
Line 71: | Line 73: | ||
</ | </ | ||
< | < | ||
- | <chokeslist> | + | <chokes> |
- | <chokes other=" | + | <choke instrument=" |
- | <chokes other=" | + | <choke instrument=" |
- | </chokelist> | + | </chokes> |
</ | </ | ||
... | ... |