-
-
Notifications
You must be signed in to change notification settings - Fork 327
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
d.redraw: Rewritten in C #3484
d.redraw: Rewritten in C #3484
Conversation
9343224
to
5a7ef2a
Compare
OSGeo#3634) Enable to use (show/add/delete/rename/query) column name which is reserved DB backend keyword.
The g.message does not need any of the session setup and it can be used during a setup process to report standardized messages to the user. This removes the need to have a full session before running g.message. GISRC is still needed, but the data (file) structures for mapset don't need to exist. The code is combination of what is in g.proj (the 'no init' call and comment) and g.dirseps (memory mode for GISRC). It is also syncing the corresponding lines in g.proj.
…o#3668) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
For reporting errors the g.message tool is called, so the environment setup is always needed (except when doing XY without errors).
* grass.script: Get GISBASE automatically in get_commands The _grass.script.get_commands_ function requires GISBASE (more specifically, path to binary executables and scripts). The need for GISBASE prevents its use before a session (more specifically the runtime part of it) is created. This changes the function to get the GISBASE automatically when not set. It also adds the standard env parameter other functions have (which is useful mainly for tests). * Add mock for tests
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…3691) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Hmm.... I think I broke it... Not sure why it's happening. My local clone looks fine. |
Replaced by #3727. |
Might be a pull instead when a force push was appropriate: OSGeo/grass-addons#802 (comment) To fix broken states, you can also force push a new branch to an old PR. Preserves comment and review history and links from other PRs. The Git mechanics for that is force pushing to a remote branch of a different name (you force push just the first time). |
This PR rewrites the
d.redraw
Python script in C. It works with #3482 to constrain redrawing within the current display extent in the monitor. Without this PR and #3482, the following test can take very long becaused.rast.arrow
has to draw 772,957,282 (number of non-null cells) arrows across the entire DEM even for a very small display extent in the monitor.#3482 and #3492 address the above issue, and this new PR resolves a similar problem with
d.redraw
because thed.rast.arrow
command will be triggered again byd.redraw
from the terminal withoutGRASS_REGION
.The basic idea is to delegate all rendering to the monitor that knows about the display extent. Modules when run from the terminal don't have that information (
GRASS_REGION
) that is dynamic and internal to the monitor.