On the demo:
Tried, gets there but appearance while so doing is somewhat clunky. Even on this modern laptop and modest demo size panel there's a noticeable intermediate (last-used) allocated colour state at NX route acceptance. Unallocated > old allocated colour > pause > new allocated colour.
?
On your potential problem where an operator selects a cab then cancels a route with a different cab before including elements of that route in a new one:
Ah, concept meets real (as opposed to ideal) operator. Concept found to be not as clean as anticipated!
Yes your suggestion would work.
?
One other though occurs, is to set the cab after the NX process rather than before it. i.e. Operator clicks cab button after rather than before. No particular preference, just another idea.
Your earlier state numbers/needed block colours:
1). Unoccupied default (one of 2). I already am choosing alternate unallocated blocks being different colours to make boundaries most obvious.
3). NX allocated default (say white as now).
4). NX allocated cab specific (one of five). Applied when cab button is clicked.
Clicking the cab button causes the cab specific allocated colour to be applied to those reserved blocks displaying the default allocated colour. This would also be a good place to select cab relays.
?
Once I've got to grips with logixNG and to some extent scripts I might have a go doing it like that. Your examples contain a lot of experience to make it so efficient and are teaching me more with every line!
?
My hardware is MERG CBUS and block relays would be a pattern of turnout events sent to CANVOUT modules with universal software. I will try that myself when ready.
