Clang whitespace

Update to master and support Geometry Nodes

Can confirm that increasing INSTANCED_PANEL_UNIQUE_STR_LEN to 5 (as @Vincent Blankfield (vvv) proposed) solves the issue.
Not familiar with the code though, @Hans Goudey (HooglyBoogly) : mind checking?

This seems to be the same as T85223: Modifiers disappear when you have multiples of them (opening old files), will merge the reports lets continue discussion there, will update T85223 wilt the file provided here.

This seems to be the same as T85223: Modifiers disappear when you have multiples of them (opening old files), will merge the reports lets continue discussion there, will update T85223 wilt the file provided here.

I can confirm this on the latest 2.93.0 Alpha, branch: master, commit date: 2021-03-04 06:43, hash: rBef7efc375197.

I am reopening this, since we have this reported a couple of times (and this report already contains useful investigation by @Vincent Blankfield (vvv))
Duplicates:

• T86101: Broken spacing in modifier panel after reordering open modifier.
• T86108: Mesh Deform Modifier Missing / not visible
• T86303: disappearing modyfikators

Will asset manager support custom node tree data blocks so such add-ons as animation nodes or sverchok could use to save some node trees?

fixed by https://developer.blender.org/rB97fabc3c1c9266e50d6b77efcb2630c38f238589, confirmed by @Erick Tukuniata (erickblender)

Use interpolate as suggested.

Still works fine on single monitor, and @Erick Tukuniata (erickblender) gave it a whirl on dual screens, lgtm!

Yes, the following blend opens three windows, the main one plus two children. The children are not full-size.

I'm on a single monitor system, any chance you can attach a multi screen .blend so i can test that still opens correctly?

@Matias Mendiola (mendio) Do you agree with the change? for me is ok.

I would like to make grease pencil able to use spreadsheet. A lot of possible uses.

One thing I would like to see in a complete design is a comparison of this and the outliner. There are clearly different use cases, but there are also apparently many overlapping use cases, especially as the scope we imagine for the spreadsheet editor increases.
Just for some examples, the outliner already has display modes, filters, a tree layout, search, sorting, and the ability to change data properties.
So I think it's essential to consider the design differences between this and the outliner, and list them clearly.

So this is what you guys have been filling those whiteboards with!

In D9415#268269, @Germano Cavalcante (mano-wii) wrote:

• Why start transforming the object if the Snap point has yet to be chosen?

In D9415#268086, @Ugo Santana (ugosantana) wrote:

Any updates on this @Germano Cavalcante (mano-wii)?

thx @Bastien Montagne (mont29) !

This is not core at all, more like UI... Anyway, will update the tooltip to "Default relative path option for the file selector, when no path is defined yet", and tweak the manual.

Adjusted according to comments, however the bug which makes handles disappear when scaling relates to this line(values of pixelx):

Thanks for the patch, I checked it and it solved T85867 as well :)

Can confirm.

@Eugene Du (APEC) I had some thoughts about combining the shield and user count, and not having enough space and using the tooltip to supplement it in this post in devtalk: https://devtalk.blender.org/t/redesigned-data-block-selector-feedback-thread/16691/67

In D10297#267999, @Peter Fog (tintwotin) wrote:

Made texts visible to a tiny size, since, text highlighting is the only way to see the unselected active strip.

Not sure if I understand, wasn't this case even before?

• Change the position slider to a percentage. NOTE: This converts the value frame from 0 - 1 to 0 - 100, so it needs to be scaled down in the draw function.
• Move the property to its own column. Borrowing from the camera passepartout as a reference.

Any updates on this @Germano Cavalcante (mano-wii)?

amazing job.
how can i use this in blender 2.93 and more ?

For user feedback on current geometry nodes, please use this topic:
https://devtalk.blender.org/t/geometry-nodes/16108

Same issue here on my Gigabyte Aero 15 running Windows 10 with an Nvidia RTX 3070. I don't see it on any other displays that I connect to my laptop, only on the laptop display.

Mockup of the blocking popup based on Brecht's suggestions (and a friendly nudge for this to be tackled for the LTS :)

Made brackets visible when very small.
Made brackets smaller(but still much larger than a vertex ;-) ).
Fixed some calculation mistakes.
Made texts visible to a tiny size, since, text highlighting is the only way to see the unselected active strip.

i have the same problem

Hello, about the geometry nodes, is there a way to add them at given coordinates, for example reading those from a text file? It's very useful to have some objects, like trees, positioned at defined position. Being able to apply the transformation makes the scene more realistic. Thanks.

@Nicholas Rishel (nicholas_rishel) Tested and crash persists, here's the paste: https://developer.blender.org/P2009

Related/similar: T86223

In T86210#1123246, @Philipp Oeser (lichtwerk) wrote:

Apparently non-8bit Images are not showing preview icons.
Fix incoming.

Apparently non-8bit Images are not showing preview icons.
Fix incoming.

In D10413#267797, @Dalai Felinto (dfelinto) wrote:

I want to share some notes to explain my concerns a bit. They all assume we keep the breadcrumbs clickable. I want to share them to build some shared understanding and language to get us on the same page. The design can go different ways, but should do so deliberately, and this should be explicit in the patch description.

• As it is, there is no way for users to know that those labels are clickable.

If you see the overlay region we have in the 3d viewport, the decoration for the menus has a solid background:

@Sybren A. Stüvel (sybren) Should this patch be abandoned now? I'm happy to update it to master otherwise.

Can confirm, will check what is going on.

I want to share some notes to explain my concerns a bit. They all assume we keep the breadcrumbs clickable. I want to share them to build some shared understanding and language to get us on the same page. The design can go different ways, but should do so deliberately, and this should be explicit in the patch description.

Please just hold on before committing this. To make it clickable as it is, it means that we are effectively adding overlay buttons in those editors. As a general rule for the Blender UI we do not do overlay buttons (or avoid as much as possible). I will check with the UI team how to proceed.

In T85841#1121668, @Bastien Montagne (mont29) wrote:

@Dylan Reeve (cadtofu) please do not set release goals yourself, only active developers should be in charge of that.

In D7685#267718, @Jer Bot (verbal007) wrote:

In D7685#266932, @Luciano Muñoz Sessarego (looch) wrote:

I think this is a feature that should go in the animation preferences, as its something you'd normally always prefer on either the tip or the head of the bone and only change it when for some reason the current place is cluttered or so, but that's corner cases.
For those I'd have it in the display of the overlays as a sort of "override" of the default set in the animation settings.

In the biweekly animation/rigging meeting, it was suggested that it be placed here to keep it next to the visibility switch, which would prevent people from having to hunt for the option.

In D7685#266932, @Luciano Muñoz Sessarego (looch) wrote:

I think this is a feature that should go in the animation preferences, as its something you'd normally always prefer on either the tip or the head of the bone and only change it when for some reason the current place is cluttered or so, but that's corner cases.
For those I'd have it in the display of the overlays as a sort of "override" of the default set in the animation settings.

Another great addition! Thanks for working on it @Fabian Schempp (fabian_schempp) !

I exported the settings using different versions of Blender and noticed that the exported file (keys_292.py) does not inform which button is used for selection, so I suspect that this configuration is not exported along with the other keys.

Whoops, didn't mean to imply that this fix corrects all related issues. Although (so far) unreported, we probably still have some issues with positioning child windows when monitors are arranged vertically, but that is caused by something unrelated and not in ghost code. Hopefully I can get to testing/fixing that soon.

I'm quite happy with this, nice job Fabian!

@Ernesto Méndez (mendezcode) @Kenny Lee (kamiyu1031) Could you recreate the crash in this build, copy the content of blender_debug_output.txt to this link, and link the result here?

In UI design there is a great difference between an "existing feature", a "user friendly feature" and a "perfectly implemented" feature.

I'm honestly not that confident about this, but it seems fine, since there are some other notifiers in slightly similar functions in this file. In any case, such an operation should be expected to redraw anyway.

• Changes based on review by Hans Goudey.
• Fixed a minor layout issue, with the space after the chevron being a bit to small compared to the space before.

Looks good. Two changes I will make when committing:

• Comment formatting: Comments should start with a capital letter and end with a period.
• Remove the "for python access" comment from the header file (since it's not quite true anymore) and move the prototype up a bit to be with similar functions.