osetrader.blogg.se

It would be cool if a an actual roster could be developed that way through automation and not have to be constantly updated. When the bus reappears like it was in the shop it will lose it's asterisk or reappear on the list. That process seems to work well for me in developing a roster if I don't have the actual roster, which I don't always have. If I could make a suggestion, maybe program in a way that a bus can be kicked out or placed with an asterisk after a month of not being in service. If so, that would be helpful to me, because then I wouldn't have to track fleets of buses for months on end. So you are saying that the database saves bus assignments for each day. I have added an archive of previous route assignments (the archive only started saving this morning, so it's not that useful yet, but I would appreciate suggestions on how to make the interface more usable.