forked from varoudis/depthmapX
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Fix pixelateLine #336
Closed
Closed
Fix pixelateLine #336
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Squash warnings on windows * Crank up warning level to /W4 on MSVC * Fix w4 warnings in MSVC * Remove some clang warnings * Remove psubvec - only used in one place and does not add real value. * Shut up warning about overload hiding in paftl (we know about it and the only way to get rid of it is getting rid of paftl) * Suppress warnings on mac as well.
…to another folder
…nto modularise_vga
…ity with previous versions
Change the actual getRows() and getCols() to size_t
Make casts explicit in readwritehelpers
Topomet no paftl
…nto apply_matrix_class
…/depthmapX into apply_matrix_class
…class Apply matrix class
…_version Add the current git-commit at the version
…nto axialmap_remove_paftl
…ve_paftl Axialmap remove paftl
…nto modularise_vga
…thmapX into modularise_vga
…esh_interface Make sure the result of the analysis is used to refresh the interface
…esh_interface Replace "retvar" with appropriate variable names
Otherwise the progress dialog runs out much faster because the whole grid is tested
…lity_progress_fix Move the progress check inside the filled-point test
When an attribute is selected from the index, the table is sorted by the same column. When a column is sorted at the table it is also selected on the attribute index
Add special handling for diagonal lines to XAXIS in pixelateLineTouching.
* Silence OpenGL macOS warnings * Remove version variable from all read and write functions * Add default case handling to all switch statements * Remove 'const' type qualifiers that have no effect * Remove communicator variable name where not required * Remove unused functions * Remove all unused parameters * Remove unused variables * Properly order initialisation lists * Fix multi-line comment * Clear ambiguity of logical operations * Add missing virtual destructors * Replace old finite() with isfinite() * Remove the register specifier * Change __max to std::max * Use std::move for SalaErrors in SalaProgram * Fix operator order * Fix other minor issues * Squash all warnings when comparing integers of different signs and sizes * Read count as an integer * Remove unused variable * Remove last version signifiers * Reimplement various glu functions Apple's deprecation of OpenGL creates a different problem here because the 3DView is coded using the old OpenGL way. Once 3DView is adapted to work as the GLView (or merged into it) then the glureimpl.h file won't be required. The license of the original file and thus the code in glureimpl.h is the SGI Free Sofware License B, version 2 and it is compatible with the GPL according to https://www.gnu.org/licenses/license-list.html * Remove unnecessary code * Remove unused functions and reduntant file * Add missing math declarations * Remove non-existant file reference * Squash some gcc warnings * Restore and expose a hidden colourscale The colourscale g_nicecolorhsb along with the relevant comment "Test a range designed to try to keep consistent saturation and brightness of g_nicecolor, and only move hue" has been named "Hue Only Axmanesque" as it's a variation of that colourscale. On the interface it appears as "Equal Ranges (3-Colour Hue Only)" * Remove qt5_wrap_cpp as AUTOMOC is set to ON
Add proper checks before advancing the position in the special case in pixelateLine to avoid creating pixels outside of the given range.
Moved to #372 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add proper checks before advancing the position in the special case in pixelateLine to avoid creating pixels outside of the given range.
Here is a test case to reproduce the issue:
Result:
Or by running the following command with the attached DXF file:
Result:
shape_250_4810.zip