- User Since
- Jan 28 2019, 8:02 PM (24 w, 4 d)
Tue, Jul 16
Wed, Jul 10
Tue, Jul 9
Fri, Jul 5
Jun 13 2019
Jun 12 2019
Jun 8 2019
Jun 7 2019
Jun 6 2019
Jun 5 2019
Closed with commit rBde836ded787d0f11d000afa790c337ab4f1bc196
Thanks for the fix, I just committed this to the branch. I hope your build works now.
Jun 4 2019
Jun 3 2019
Jun 1 2019
I think Brecht already answered your first question. "None" means the operation has no affect on the rotation of the 3D cursor. What would you suggest as a better name for the option?
May 31 2019
May 30 2019
In order for the report to be useful, you'll have to provide more information. What are you doing when it crashes? Can you find some sort of pattern in the "random" crashing? Without that info I don't think the developers will find the report helpful.
Do you mean using the "None" orientation preset for the 3D cursor placement active tool? I don't see that setting in the "View" tab of the sidebar, I see it in the "Tool" panel.
May 29 2019
May 28 2019
May 23 2019
May 22 2019
May 17 2019
May 16 2019
May 15 2019
Yeah, I didn't mean to keep the skip save in.
May 12 2019
Hi @Brecht Van Lommel (brecht). I wanted to remind you about this patch in case it had fallen off your radar. It would probably be good to get it in sooner rather than later because of the small change to the python API it includes.
May 7 2019
May 5 2019
May 1 2019
Forgot to change CUSTOM to WORLD in two places.
- Added Object Add 3D Cursor Align preference to go along with the view align preference.
- Simplified change in add_object_align_init.
- object_utils.py object add helper obeys object add view align preference now.
- Changed Custom to World alignment. It's clear that it's adjustable because it's the default and it's a less confusing word.
I just saw this, I'm sorry I duplicated some of your work. This is a popular issue I think :P
Resolved problems, updated object_utils.py, removed WORLD option
Apr 25 2019
Thanks for looking at this Brecht!
Apr 20 2019
Cool! I changed it to "Custom."
Changed "Input" to "Custom" like Pablo suggested. I found a few other examples of that term used in the UI, it's definitely better. Applies to latest master.
Apr 19 2019
Apr 18 2019
Here is an updated version: D4706
Apr 11 2019
This looks like a problem with object_utils.object_add_grid_scale_apply_operator(self, context) on line 245 of add_mesh_torus.py.
If this doesn't happen anymore (I tested it too, it looks fine), I'll close the issue.
@William Reynish (billreynish), I'm not sure a paradigm of a tool having two sets of settings really makes sense. To me this seems like a good way to make the top bar more useful and reduce confusion.
Apr 7 2019
This diff was getting a bit old, so I've updated it and made a few improvements too (IMO).
Mar 25 2019
Mar 24 2019
How is this? D4583
Mar 20 2019
I want to take this on!
Mar 19 2019
I think I agree with Dan here, although there are good reasons on both sides. I'll try to sum them up here:
Mar 18 2019
Oops -_- I didn't mean to add Campbell also, sorry.
I've made most of the changes here:
- Redraw after cursor is placed. (Right now it only repaints after a cursor drag action.
- Add reset button for location.
- Position lock? This would probably better built in to the location property somehow though.
Mar 14 2019
I've been pursuing this for a bit. I thought I would provide an update in case it was helpful to anyone:
Mar 8 2019
I thought it would be worth it because I end up naming most of the primitives I add in many workflows anyway, so it saves a step of finding it in the outliner or properties.
Feb 27 2019
Feb 26 2019
Feb 25 2019
EDIT: oops, I misundertood what you did. Even better, now I get to learn from it.