-
Notifications
You must be signed in to change notification settings - Fork 153
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
Added configuration option to suppress large data warning #999
Added configuration option to suppress large data warning #999
Conversation
Thanks, this looks great! I'll test this out today and will merge it if everything works fine :) One quick question to ponder - should we make the setting be the reverse of what it is here, i.e be 'emit warnings if data is large' and have it be ticked by default? |
Personally I think it's best to have warnings on by default, and then let users turn them off, as otherwise users could easily get frustrated (or think Glue has crashed) when trying to plot large datasets. However, it's very much a matter of taste, so I'm happy either way. |
@robintw - just to clarify, I also think warnings should be on by default, but I meant that maybe the option should be |
@robintw - this will need to be rebased, I think due to a small conflict in |
I must admit that I've never really understood rebasing. What should I run to do this? |
@robintw - no problem. Rebasing means playing back your changes on top of the latest developer version. Let's say that you defined the main glue repository as being called
You can start off by fetching the latest changes from upstream:
then, on your
You can review the commits in your branch in the editor that comes up:
then save to continue (without making any changes). It will then proceed to replay the changes you have on top of what's in the latest developer version. At some point, it will complain about a conflict:
You can do
open that file, and the conflicted region will look like:
Basically I had changed the developer version to remove
then save and quit. Then you can do:
followed by:
and you should be all set. Once this is done, just force push your branch to GitHub. Let me know if any of the steps don't make sense! |
@robintw - by the way, if you run into any issues, we can also chat live at https://gitter.im/glue-viz/glue-geospatial |
…splaying the warning dialog when viewing large datasets
13bc443
to
31ad416
Compare
…e in reverse (ie. True is default, and shows warnings, turn off to suppress warnings)
Thanks @robintw! |
This is my first proper PR for this project, so please let me know if I'm doing things wrong.
Specifically, I haven't edited
.ui
files for Qt before, so I may have done some dumb things there...This fixes glue-viz/glue-geospatial#6