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

Change the load dialogue to make the load messages more visible #342

Closed
ljramones opened this issue Jan 15, 2022 · 6 comments
Closed

Change the load dialogue to make the load messages more visible #342

ljramones opened this issue Jan 15, 2022 · 6 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@ljramones
Copy link
Owner

as it says

@ljramones ljramones added the bug Something isn't working label Jan 15, 2022
@ljramones ljramones added this to the v0.7.1 milestone Jan 15, 2022
@ljramones ljramones self-assigned this Jan 15, 2022
@ljramones
Copy link
Owner Author

THese are Chuck's comments

Selected 270 LY csv file for loading/adding dataset.
Process was under way.
It indicated that 20000 of 20000 stars had loaded.
I clicked on it.
The table disappeared.
I looked for the dataset. It was not there.
I figured the load had failed and tried to add it again.
TRIPS told me it was still loading. However, there was no box or other processing advice/warning on the display to indicate this at all.
It finally loaded and plotted when I went away.
I think if a process is still underway, there needs to be something on the display which indicates that. Maybe blinking if it’s actually pausing/impeding other activity.

@ljramones
Copy link
Owner Author

load dialogue is now more responsive.
I update the feedback more by dropping the report rate from 20,000 stars per update to 2,000 stars per update
I put the loading message in a larger bold red font.
I think its fixed and if needs be, we can reopen

@cegannon1
Copy link

cegannon1 commented Jan 15, 2022 via email

@ljramones
Copy link
Owner Author

There is no way that I can apriori know how many records are going to be loaded.
Originally, I would have the first value be the number of records per update and the second number be the cumulative total. So 2000 of 2000 then 2000 of 4000.
I decided to just give a cumulative total. I can't show how far along it will be.

@ljramones
Copy link
Owner Author

It actually will show you 20000 of 140000 if you wait long enough.
Early on, it loaded very quickly, but since we increased the complexity of each line and number of data items, its really slowed down.
On a less powerful computer, the time between updates is going to look like it's hung and not doing anything.
I changed the load factor form 20,000 to 2,000 to give a more responsive update message.

@cegannon1
Copy link

cegannon1 commented Jan 16, 2022 via email

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

No branches or pull requests

2 participants