Maybe this makes a fine candidate for @Campbell Barton (campbellbarton)'s custom manipulators at T51844

In D2751#65481, @john peterson (bliblubli) wrote:

Very helpful for review. It's a pleasure to see a student with so long commitment.

I'd vote for tucking it away in the right-click menu too. Less visual clutter, no accidental deletions, and it could help make the pulldown menus more visually consistent.

I know this is a work in progress and not finished at all, but I'll leave a few unsolicited suggestions if I may; purely from a mere user point of view:

Cool, lets get this into 2.8! :)

Whooaa! Thanks for changing this behavior. It has always bothered me, but since I don't use it very often I just thought I was the minority here, and it was required for everyone else's workflow.

Oh, sorry, here you go.

Could not recreate here under Windows 7 64 bots Blender 2.78, making duplicates real for both groups defined in the provided file worked as expected.

In T51844#441270, @Campbell Barton (campbellbarton) wrote:

@Duarte Farrajota Ramos (duarteframos) - ok, see what you're getting at, still some Q's remaining.

• Would this be object-mode, edit-mode... both?
• How would this co-exist with the transform manipulator?

Ah true, didn't think it all the way through about when/where to show said manipulators.

Some humble suggestions

Better snapping system is a very important and necessary for a lot of people doing more kind of "precision" or "hard edge" modelling work.
The proposal at T45734: Grab, rotate, scale with basepoint holds some really promising results that I would love eventually see implemented, one way or another.

In D2445#61567, @João Araújo (genio84) wrote:

4. I have renamed "Extend" to "Intersect" and "Batch Extend" to "Extend".

I was about to report this too. With particles set to Hair type or Emitter type, and 1 particle per face, on an arrayed plane, matching the particle count to the exact number of faces produces a similar behavior.

I use Blender daily, but I don't frequently make animations so take it with a grain of salt, I don't have a strong opinion here.
Quite frankly I am one of the 'guilty' users that never used the Animation Player, in fact up until now I was not even aware of its existence or what it did exactly, though I've heard about it before.
If no GSOC student takes it, maybe this could eventually boil down to: Do people really use it? and Are there any decent third party/external alternatives?

I don't find Blender's tooltips bad at all, they are actually quite good. Just some times missing, one specific example of this is for most Cycles nodes properties and sockets tooltips.

Well they all look especially awesome, particularly the "Slight Fresnel on the wires." one. Congrats to you devs for the awesome work, can't wait for 2.8!

In D2566#60039, @Julian Eisel (Severin) wrote:

this is more meant to make it easier for people to do these changes and submit them for master inclusion. (...) It could be a great way to improve our tooltips based on the new guidelines. And everybody could help doing it, not just devs ;)

For context this comes as a from followup for a Blender Stack Exchange question.

From a user point of view I would not mind tucking them away into the popup at all, in fact I would encourage it.
I don't mind the additional clicks required, adding or removing Scenes/Layouts/Workspaces should not be that common task that it requires being always visible, I would value much more the saved space and cleaner UI. It would also add the benefit of allowing removing items other the just the current one.

Totally support this idea. Ideally I in place of a stadalone "Collections Editor" it would all be done through a reworked Outliner with proper support and navigation.
Having a "Collections" mode in the Outliner where one could drill down the all the available Layers, Collections all the way down to individual Object would be my dream scene organization tool.

In D2445#58183, @Sergey Sharybin (sergey) wrote:

Steps: With this file run Trim tool (i do it from spacebar menu) and the error will appear: Cyclic splines needs at least two intersections

In D2445#58197, @João Araújo (genio84) wrote:

I see. The problem with that solution is that the approximation to a "real fillet" (best approach to a circle) can only be as good as the artists' eye. Chamfers become trivial though, but I'm guessing I will no longer be able to allow you to control the angle.

In D2445#58166, @João Araújo (genio84) wrote:
I overlooked that comment. Believe me when I say I tried to do it! But for some reason the input would not accept negative values! I'll give it another shot.

In D2445#57872, @Sergey Sharybin (sergey) wrote:
Not really happy about two extra options for such a little thing here. Can at least get rid of revered direction and allow negative values for the extrude?

Very welcome improvement, certainly handy!

Ah yes, I see, I always like knowing a bit more about the inner workings and technical side of Blender.
Thanks for the thorough explanation :)

Cannot confirm in Windows 7 64bits. Steps to recreate aren't very clear

Instead of three separate lists could we have "Drawing Support", "Scene Elements" and "Screen Effects" as categories or groups (like proposed layer groups) inside the same list?
They could be expandable showing the sub-items, and they could have a "master toggle" eye icon that would quickly toggle visibility of all sub-items overriding any child.

Ok, I seem to have made some headway in pinpointing the source of the crash, it seems to be something related to material slots.
Reported curve in attached file has no materials nor material slots assigned, but simply creating a new material slot, even if no material is added, will no longer cause a crash upon rendering.

Man you guys are quick!
Thanks for the quick fix, looking forward to this.

Tested also on Windows 7 64bits with a GTX580 + GTX980Ti on official release of 2.78 and could not recreate.
Resized through size sliders and scale sliders and no crash

Certainly, here is a demo file.
Browse

I second what lower case said, SVG curve objects are often imported with a very very small size, or even at the correct size but with a very large or very small scale factor.
When scaling them one must then enter edit mode, after applying the scale, and then set the radius of all points back to 1 otherwise extruding/beveling will fail yielding very strange results.

Sorry for the delay in replying, here is my node group setup for cycles cube mapping.

Ah I see, that's right. I did manage to make my own "Cube Mapping" custom node that masks he mesh faces through normals and applies the correct projection to the face.
It can easily be modified to fade smoothly between normals and with an even more complex node setup it could have more "normal steps" for more accurate projections on curved surfaces, but as you mentioned it will create visible seams and is bound to fail sooner or later if the mesh is more complex.

Please forgive me if I am missing something trivial here, but I am an architect working daily in Blender and rendering in Cycles (hell I am doing it right this very moment ;) ) and for a very very very long time I ached for something like this in Blender.
It was my number one feature request for a while, I also though I wanted that "UV Modifier" like 3DSMax has one, and I even went through Sure UVW mapping addon and alikes. That is until I learned how to use nodes properly.

True, I can also confirm that, typing something like path\to\some\blend_file-blend\Lamp\ or path\to\some\blend_file-blend\Groups\ prompts the user to "create new folder ?" but then fails.
It never navigates to the desired "virtual datablock folder".