-
Notifications
You must be signed in to change notification settings - Fork 13
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
Help/Examples: Toolbar's Up button loses classification progress (back button doesn't) #6
Comments
Have you seen the Examples? For each question you can click on the ? icon (or it might just be "Examples" in the menu, depending on your device). That has explanatory text and example images. |
ok, now that you mention it, there is. I thought, when I clicked on the ? icon that this was it. Maybe you add a comment that there is more for each set of questions. On the other hand, if I click on the ? half way through the questions and I go back the questions start all over again. That's a bug in my opinion. The app should remember where I clicked the ? and go back to that point. |
I don't see that - it would definitely be a serious bug. Could you please double check that? Is it happening consistently? |
About the lack of an introduction, I have to keep the UI as similar as possible to the web UI: In theory, any extra explanation that I give could influence the results. |
The help screens are good. I've checked them. Some are too wide though, I'll add an image. And yes, the screen keeps going back to start. Also, after checking, if I click on an example image, e.g. the bar galaxy screen with many examples and then click on the return button at the top left it returns to the original help screen. Maybe I'm doing it all wrong :) |
Yes. I've just opened a bug about the image cut-off bug: |
Sorry, that doesn't make perfect sense. Do you mean "orginal question" rather than "original help screen"? Could you please write down the exact steps so I can try to reproduce it. I know it takes time but I haven't managed to reproduce it myself. |
Actually, I think I have a fix for this already. Soon I'll release a new version for you to please test. Would you like to join this Google+ group so you can get it as a beta before I risk releasing it to everyone? |
Sorry, been a bit too busy elsewhere the last days. I'll keep this issue in my inbox so I'll get back to it asap. The latest release fixed some issues, the biggest problem is still with the return button in the Galaxy Zoo bar (upper left corner). This keeps returning me to the start. Also going back is somehow missing. I have to leave the app and open it again to start over in case I made a mistake. |
Please report every issue that you find, ideally in separate bug reports.
Please:
There is a "Restart" menu item. It will appear as an icon in the app menu (curving left) on wider screens. Do you see that? |
Hi, just tested today's version and most seems fixed. I noticed:
|
Yes, some of the questions have no example images. That's an issue with the Galaxy Zoo website, from where we get the questions, answers and help/examples. For instance: zooniverse/Galaxy-Zoo#181 Could you please report separate issues in separate github issues?
This is the same issue you talked about before, right? Please: b) Write down exactly the steps that you take and exactly what you see. That gives me the best chance to reproduce this. |
Thanks very much for taking the time with that and for figuring out that it's a problem with that particular toolbar back button. Now I can reproduce it too and I'll investigate. |
Fixed, I think: da13474 But please check when I release the new version a couple of days from now. Thanks again. |
Yes, fixed. Thank you very much. |
I've only just released 1.32 with the fix now (though it was in Beta for a few days). |
I've got it via F-Droid a few days ago. |
Hi there,
I checked out your app and like it because it's somehow relaxing. Nevertheless, I don't really know what I'm expected to do. All I do is answer the questions to my best knowledge. It would really help to have a walkthrough to find out how to best answer the questions.
The text was updated successfully, but these errors were encountered: