Skip to content
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

better feedback on querying TPL #151

Open
mfrasca opened this issue Aug 1, 2016 · 5 comments
Open

better feedback on querying TPL #151

mfrasca opened this issue Aug 1, 2016 · 5 comments
Assignees
Labels
ux ux bug

Comments

@mfrasca
Copy link
Member

mfrasca commented Aug 1, 2016

something I find confusing: as of now, when you click on the sp_species_button button, the software starts looking up the data, but does not tell you in any way.

it would be nice if you would immediately get to see a message box informing you that ghini is looking up your data on TPL.

@mfrasca
Copy link
Member Author

mfrasca commented Aug 1, 2016

the above goes in the message box before we invoke the callback.
the callback should distinguish and clearly report the failure cases:

  • request times out (we abort)
  • server reports an error (they abort)
  • request results in something I can't use (I don't understand the answer)

mfrasca added a commit that referenced this issue Aug 1, 2016
…age as soon as we have a response and handle it.
@mfrasca
Copy link
Member Author

mfrasca commented Aug 8, 2016

good enough for ghini-1.0, postponing the remaining issue to 1.1

RoDuth pushed a commit to RoDuth/ghini.desktop that referenced this issue Dec 30, 2017
@mfrasca mfrasca removed the ghini-3.2 label Mar 28, 2018
@mfrasca mfrasca added this to the Tanager-2018-08 milestone Aug 20, 2018
@mfrasca mfrasca removed this from the Tanager-2018-08 milestone Sep 1, 2018
@mfrasca
Copy link
Member Author

mfrasca commented Oct 25, 2018

it happened again:
image
and from ghini.desktop you have no clue of the reason for not getting an answer.

@mfrasca mfrasca self-assigned this Oct 25, 2018
@mfrasca
Copy link
Member Author

mfrasca commented Oct 26, 2018

compare with issue #440

@mfrasca
Copy link
Member Author

mfrasca commented Oct 31, 2018

they fixed the issue on their side, but we still have to do something on our side, to avoid getting stuck and to inform the user on what is going on. compare with #458.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ux ux bug
Projects
None yet
Development

No branches or pull requests

1 participant