| Age | Commit message (Collapse) | Author |
|---|
|
Fix a few speling issues in comments.
|
|
The Fillet Vertices command was inadvertently shadowed by the newly introduced View Normal command.
The View Normal command now uses 'n' as its mnemonic.
|
|
|
|
|
|
System would not move selected vertices to an absolute location in Edit Mode.
This was caused by system not recognising selected vertices.
|
|
This enhancement enables the user to work always Normal to the View
as defined by "Working Plane" in PDT Design Functions Section.
For example: If the working plane is set to Front and the Operation is "Extrude Geometry"
the system will extrude along the Y axis by the amount specified in the "Distance" Entry Box.
Specifying Working Plane as "View" cause the system to work always Normal to the current
view orientation, i.e. into, or out of your screen.
This enhancement is only available for Blender 2.9x builds.
|
|
|
|
Fillet Radius and Tanget Radii were not defined with unit="LENGTH", causing problems when Blender Units are set to Imperial.
|
|
Reduces warnings while running tests.
Also fix some descriptions with strings concatenated but without a
space in between.
Reviewed by campbellbarton
Differential Revision: https://developer.blender.org/D9655
|
|
The tool still used the "vertex_only" argument to the bevel operator,
which changed in 2.90. This commit also fixes the same error in the
Mesh Tools addon.
|
|
This resolves one of the last few areas where we still use inappropriate
abbreviations. Reading abbreviated words is usually slower, because
users must parse, guess and translate the words. Using abbreviations
such as 'rot' is also especially bad since it's a word in itself too.
The main advantage of abbreviations is that they are faster to *write*,
which just isn't a concern for text in the UI.
|
|
An issue occurred if you opened Blender with a new file where the
Parts Library path pointed relative to the Blender App, not the working
directory, so was not found.
The Parts Library file is now moved to the Parts Library Menu, so must
be set for new .blend files. Existing .blend files are not affected by
this change.
Error message altered to reflect the option of having this Parts Library
live anywhere.
New Feature: Add Trig Waves Functions
Requires the user to select an existing object in the Trig menu.
|
|
|
|
|
|
Made functions more understandable by improving DocStrings
|
|
This enhancement allows users to move Empties, so they can be used as a parent
object for other objects. Allows movement by Delta, Direction and Absolute.
|
|
This commit is still WIP.
Added Enumerator for Tangent Types, refactored code, revised DocStrings.
This section of PDT still requires extensive testing, currently underway, but not complete.
|
|
This is still WIP.
Further expand options to work in any plane and from selected vertices.
DocStrings Added. Code refactored.
Further testing is still required before this can be released for general use.
|
|
This Branch is WIP, still in development and not yet suitable for a release.
This process will add the ability to draw tangents from a point to an arc, or circle.
It will also add the ability to draw tangents, both inner and outer, between two arcs.
Arc centres and radii can be manually input into the UI, or set from three vertices that
lie on an imaginary arc. Tangent functions have their own PDT Sub-menu.
This commit only works in Front view, to get the maths right, later commits will expand
this into any view orientation, using existing PDT code.
This commit does not contain DocStrings for the new pdt_tangent.py file, these will
also follow in a later commit.
It is recommended that this commit is not used in a production environment. Once
complete, a new version Branch will be added, at this point the code will reach Alpha
status and be appropriate for extensive user testing.
|
|
Add local view orientation options to Delta & Direction options for all functions.
|
|
Minor error, there is no need to check for vertex type if adding a new vertex
by absolute coordinates.
|
|
|
|
Modified help information in PDT Command when user enters ?, or "help".
Added Wiki URL and some minor changes.
|
|
In certain circumstances, where the user has unwisely set inappropriate inputs,
modes of operation, or other settings, some errors were not trapped. This fixes those
making the system more "User Proof". A new exception was added if the user works
in an inappropriate feature setting, like Face mode when Vertex mode is required.
|
|
Attempts to Append, or Link Objects, Collections, or Materials when not in Object
mode resulted in a system error. This is now trapped as an Add-on error and
reported to the User.
|
|
This fixes a small obscure error in Absolute mode whereby Bmesh was not
always found if Absolute mode was used.
This became apparent if no object was selected and an attempt was made
to add a new vertex, or extrude vertices.
Other checks did not trap for this error. These traps were originally
stored in the individual functions, now all traps are moved to the
command parse function.
|
|
Fixed a small error in New Vertex placed at Absolute Coordinates.
This error was very hard to detect and only occurs in very odd circumstances
It no longer occurs, a similar error might have also occurred with Extrude Vertices
to Absolute location, this fix also prevents that.
|
|
|
|
All Docstrings have been examined for typos and format, etc.
Small code change to set Selection Mode to "SEL" if operation is not
"C" or "P" to avoid possible errors when using other operations.
|
|
|
|
The error likely came about because we first commit files to @clockmender's
upstream github repo and then use git format-patch to create patches which
are then applied to the blender add-on repo with:
`git-am -3 --rerere-autoupdate foo.patch`.
Here, the issue seems to be that we've renamed files in the upstream github
repo, but that I then failed to first create and commit empty files with
the same name in the precision_drawing_tools/ repo, which meant that git
did the best it could and added them to the root of the blender add-ons
repo since the files didn't exist in the add-on repo index when they were
added.
|
|
This concludes the refactor of the functions and operations in v1.1.8.
Overall, no significant new features were added, but several inaccuracies
and corner cases were fixed during the refactor and docstring review.
|
|
|
|
|
|
Make sure Pivot Point is updated when moved.
|
|
|
|
- Remove unused imports
- Add comments where appropriate
- Improve readability of variable names
- Re-implement a couple of functions using dictionaries instead of if-statements
- Results of Pylint & Black operations, plus some fixes to code.
|
|
Maths Operations did not exit on completion, resulting in possible selection errors.
|
|
Applies system rounding to inputs as defined in Add-on Preferences.
Default is 5 places of decimal, values taken from UI, or by calculation are
rounded before command is submitted.
|
|
- Check Object Mode is either EDIT or OBJECT as appropriate.
- Change If loop to check command values - error if D, E, For M commands.
- Remove surplus command check in command_maths function.
- Added import of exceptions file.
- Check for Mesh Objects in Object or Edit Mode first and exit with error
message if not.
- Some minor changes for obscure failures in unusual circumstances.
- Fixes and changes to code to correct minor errors and remove unnecessary
checks.
- Refactored Command File structure.
- Add more checks to Fillet Operation to check selection and make sure
current selected vertices/edges are always used. Previous version could
use wrong selection if Bmesh SelectHistory was in place for Faces, or Edges.
|
|
Most of the recommendations from pylint are now done, I have not changed variables
like v in expression [v for v in... as I consider these to be normal coding practice.
Rename pdt_com_functions.py to pdt_command_functions.py
Fix error in Intersect operation if selected vertices resulted in more than
2 edges being selected. Priority is given to two edges as a selection, then to
4 vertices, if the four vertices represent two edges, the intersection point is
at the intersection of the two edges, which might not be the four vertices, if
one of the vertices forms part of two edges that are also selected.
Priority is 2 edges, then 4 vertices selected individually with the mouse.
|
|
Moved all PDT Design Operations and Tools to Command Line file to de-dupe
code. All can now be called from the command line, e.g. a command of "otc" sets
the active objects Origin To Cursor, etc. Needs extensive further testing to see if all
Operations in all Modes still work exactly as before.
Tools menu split out from PDT Design so it can be minimised when not in use.
|
|
Commands like ni20,45 did not work because there were 2 mode == "d" clauses.
Replace one mode == "d" clause with a mode == "i" clause.
|
|
Fix bug where if selection was not made by cursor select, an error occurs in
placing cursor, pivot point, adding edges by percentage, etc.
|
|
|
|
Also ignores blank commands rather than showing an error message.
|
|
|
|
Fix error whereby some appended objects through PDT Library did not get moved to
cursor location.
|
|
The menus now are re-arranged according to the width of the UI.
A cut-off value is set in the Add-on Preferences.
Remove vestiges of automatic UI highlighting experiment.
|
|
|
