-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bus stop filter usability #790
Comments
@btrem are you using the iOS app? |
@aaronbrethorst yes. Sorry, I probably should have noted that. BTW, I thought maybe I'd poke into the code and see if I could provide a solution/PR, but I can't find anything. What language is OBA written in? |
@aaronbrethorst ah, I just noticed that you transferred this to oba-ios. I didn't realize that there was a separate repo for that platform. (Funny that, because I thought I might try to create a PR to solve this issue, but couldn't find any code in the base oba repo.) So, um, yeah, sorry, I should have looked through the repo list more thoroughly. me/ grins sheepishly |
Hey @btrem , thanks for reporting this! I see the issue with the filter causing problems for single-route bus stops. I'll take a look and discuss with the maintainers about potential fixes. 👍 |
@btrem no worries! the most important thing is that you logged the bug :) |
Problem
I use a bus stop that, for the last few months, showed no arrival info,, even though the transit agency's website reliably reported bus arrivals. Turns out the the stop was filtered, so I must have accidentally tapped the filter button at some point, but not selected the one bus to show. And since the stop only serves one bus route, there was nothing to show.
Solution
I think maybe there should also be some notice, below warning, to inform the user that the stop has been filtered, but maybe screen space is too limited.
The text was updated successfully, but these errors were encountered: