-
Notifications
You must be signed in to change notification settings - Fork 103
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
New Data Frame #4971
New Data Frame #4971
Conversation
updating master
Updating Master
Updating Master
Data frame pato whiz
This reverts commit 2057760.
Data frame pato whiz
Updating Master
@africanmathsinitiative/developers this is now ready for review |
@Muthenya @JacklineKemboi @shadrackkibet can someone test this please? |
Updating Master
Should we have yellow for incomplete columns and red for columns with an error? |
It depends what you mean by error. An error in the R command (which we want to implement later) could have just the cell highlighted in red. |
We have a message box outlining this. It tells the user that there's a duplicate. I don't like preventing the user from leaving a control. It goes against the rules of a good UX. For instance the user could want to correct the other cell not the current selected one |
Ok that sounds fine. Then I think we have it highlighted in yellow too, and reserve red for when we check errors in R code. |
Okay. We will have red for invalid column name and invalid expression |
Invalid column name to mean it's a reserved R keyword |
Testing this again. |
I have tested this and it now works better. @dannyparsons this is ready. |
I'm getting a few inconsistencies here. Firstly, it only shows one incorrect cell at a time. When I had multiple gaps only the first one was highlighted in yellow. It would be good to check all cell and not stop when an error is found. Because of this, I could for example, type an invalid column name, but it didn't show as an error because an earlier cell was empty. It's good that OK was always disabled when I had something wrong. It never let me click ok when rows were incomplete or had invalid/duplicate names. |
@dannyparsons should we then remove the message boxes? they will be annoying if that's the case |
Yes we probably don't want multiple message boxes appears each time a cell in changed. |
And how will the user know what S/he is doing wrong? |
I was going to suggest a tooltip on the problem cells, but that might be too much work. |
Lets just leave the messageboxes then. |
Sounds fine. |
@dannyparsons this is ready for your reveiw |
@dannyparsons this is ready for your review |
2 similar comments
@dannyparsons this is ready for your review |
@dannyparsons this is ready for your review |
This is ready other than the 2 spacing issues. |
Co-Authored-By: Patowhiz <[email protected]>
Co-Authored-By: Patowhiz <[email protected]>
@dannyparsons changes applied |
Fixes #4439 Extending the File > New dialogue even more.
@africanmathsinitiative/developers this is ready for review