a-b-street / abstreet

Transportation planning and traffic simulation software for creating cities friendlier to walking, biking, and public transit
https://a-b-street.github.io/docs/
Apache License 2.0
7.66k stars 340 forks source link

Input signal timing using keyboard when setting intersection timing #499

Open belt-drive opened 3 years ago

belt-drive commented 3 years ago

It looks like the only way to change signal timing is using the up and down arrow buttons on the "Edit intersection" interface. This makes for an unpleasant experience when you want to do big edits on 2 or 4 nearby intersections (i.e. changing signal timing from 30 to 90 seconds for some phases). It would be very helpful to be able to enter the number of seconds per phase using the keyboard.

I personally would also prefer if intersection timing were quantized, maybe in 10- or 30- second increments. That makes it much easier to match adjacent signal timing. It also makes for fewer clicks when adjusting signals (although I recognize that this request is to provide an alternative input mode than using click buttons. I'd say either direct keyboard entry for signal timing or quantizing the time into larger chunks and using only the up and down buttons on the interface would work).

dabreegster commented 3 years ago

+1 to both ideas! I'll discuss with our UX designer. We abuse the "spinner" widget in many places today because the text entry widget is even worse.