- User Since
- Aug 24 2011, 12:06 PM (399 w, 3 d)
Mar 13 2019
Solved by Blender developers themselves in https://developer.blender.org/rBcae89a6889e0fc03130a56b6bf84e257eaff0fec
Feb 27 2019
By the way, some functions (rna_Object_select_get, rna_Object_visible_get, ...) are missing the view_layer parameter and always get the selected/visible/etc. state from the current context's view layer, while other functions (rna_Object_holdout_get, indirect_only_get) require to specify the view layer explicitly. Is this an oversight or an intentional design?
Feb 23 2019
Feb 12 2019
Thanks! layout.popover() seems like exactly what I need.
It's just a matter of (width, height) arguments of invoke_popup() not being multiplied by the ui_scale.
I'm talking about the size of the dialog box (width, height).
(Added extra test case - properties with non-empty labels also cause shifts)
Feb 11 2019
Apr 24 2018
Jan 8 2018
Sorry! I'm so stupid :-(
Mysteriously, this change in semantics somehow did not affect my 3D cursor addon in perspective view, and I only learned that there's a problem when a user pointed out that the addon's snapping doesn't work correctly in orthographic view.
Jan 7 2018
Dec 3 2017
May 2 2017
Apr 5 2017
stefano, I tried to create a scene which contains a cylinder and another object with a particle system, but there seem to be no problems with exporting to OBJ. Can you share the .blend in which the problem is present, so that we have exactly the same test case?
stefano, what objects were you trying to export? To which format? With what export settings? Can you share the file you were trying to export from?
Just in case: what version of Blender do you use?
Mar 29 2017
Regarding the error: you seem to be using an old version of the addon. The latest version shouldn't have this problem.
Feb 20 2017
Those are fully internal guts
Er... Can something that is clearly accessible to the user (Ctrl+Alt+Z) be considered "fully internal"? The basic logic behind proposals like these is that if users are able to see and/or manipulate some part of the program's state, it's reasonable to expect that it should be accessible to the scripts too.
Jan 15 2017
Nov 25 2016
Nov 18 2016
May 17 2016
If this addon will become obsolete, I would be extra happy :-)
I implemented Cut primarily for the sake of completeness (users accustomed to other programs would expect to be able to do this), but there are some cases when it might come in handy:
- moving objects between files and scenes: more intuitive/quicker than [Copy, Delete, Paste].
- moving geometry data between objects: more intuitive/quicker than [Copy, Delete, Paste] or [Separate, Join].
Perhaps it might be a good idea to ask on forum/mailing list for other possible uses of the Cut.
Mar 25 2016
В консоли (меню Window -> Toggle System Console) какие-либо ошибки выдаются? Напишите мне приватное сообщение (например, на blenderartists.org).
Mar 24 2016
Strange. It works as usual for me in 2.77. Where/when did you download the addon?
Whether or not the cursor snaps to the grid line intersections depends on the "relative coordinates" option in the "Transform Extra Options" panel (in the Properties Shelf).
Mar 5 2016
Ah, I suppose I should mark it as "resolved".
Sorry for the delay.
The problem was actually caused by the change of the ray_cast() return value in Blender 2.77, so snapping didn't work at all.
It should be fixed now.
Dec 5 2015
Uh, hope I won't un-archive it by replying? "^^
Sorry for such a late reply,
Jul 1 2015
Seems like I managed to fix the issue with tooltips/node-dragging. It was caused by the approach I was using to auto-register keymaps at the addon start-up.
I have replaced the old modal operator running in background with scene_update_post callback, and the bug disappeared.
If I won't be able to find a solution today, I'll probably just delete the addon from the contrib.
Jun 7 2015
I and Ivan Santic have been involved with addons that deal with multiple-object value editing. Perhaps our results can be of some help too?
Jan 20 2015
I know about this bug, but I won't be able to fix it quickly. It's caused by keymap auto-registration; for now you can try to turn off the keymap auto-registration in the addon preferences.
Jan 12 2015
Nov 30 2014
Nov 25 2014
Jul 28 2014
Ah, sorry, I updated the file but forgot to update the version number in the wiki.
I've removed the export options that cause Blender to crash on .blend-export (they are outdated/deprecated anyway by now).
See my private message on BlenderArtists.
I'm afraid I the information you provided is not enough to figure out the problem.
Can you share the .blend you were working with and the detailed instruction for reproducing the effect?
Jul 25 2014
Thanks, I've now added handling for the situation when there is no active object in the scene.
Jul 24 2014
Hmm, I can't reproduce the error on my computer (I have Win 7 32bit, Blender 2.71 official build). There was a similar error reported a couple of months ago, but I fixed it back then.
Dec 21 2013
Then the effect you're referring to is probably caused by the "Triangulate" option of the .dae exporter.
"Triangulate" is enabled by default and is located at the bottom-most panel of the Collada export settings.
Dec 18 2013
zfadarkness, I couldn't reproduce your problem in a test scene, but I found and fixed a couple of bugs. Get the most recent version, maybe it would work correctly for you now.