@Julien Kaspar (JulienKaspar) Could you prepare a simple file with these corner cases to use for doing some test? I'm thinking to prepare a simplify using the distance between points, and I would like to have a file for testing.

@Antonio Vazquez (antoniov) @Matias Mendiola (mendio) @Daniel Lara (Pepeland) (pepeland)
I agree. The optimal drawing feel should be most important. The suggestion of the even spacing of points will feel worse and will make details get lost with to wide spacing but in certain corner cases can have a curve that's easier to work with. The simplify & adaptive simplify are great additions but don't solve the problem of massively uneven spacing or extremely dense curves.
The spacing option could also be used for drawing regular poly curves. I hope that these will share a lot of functionality with grease pencil at some point since grease pencil is so much more advanced now.

Yes, keeping accuracy of the final strokes is so so important. drawing with acurracy is the key for a good workflow in 2D tasks, like @Matias Mendiola (mendio) said, more than 80% of the time used by the artist with Grease pencil is freehand drawing,
for this reason we create a group of functions in grease pencil brushes to improve the the drawing accuracy.

Thanks @Antonio Vazquez (antoniov) for the clear explanation. I agree with you that the main risk with this change is to lose the pleasant feeling that we have right now while drawing with Grease Pencil (more than 80% of the time used by the artist with Grease pencil is freehand drawing).

Regarding this task, there are several points we must consider.

@Antonio Vazquez (antoniov) the issue was with freehand drawing.

Thanks, committed with edits so it matches vertex/texture paint opacity.

@Campbell Barton (campbellbarton) You are talking of free drawing an stroke or darwing a curve using primitive tool? it's not clear what you mean with "draw a curve", maybe you mean draw a "stroke".

@Charlie Jolly (charlie) Could you take a look?

I added this feature to the sculpt-mode-features branch rBbc7068c4b9130a00116cef52fd5cc27926a63717

We don't usually use icons for these kinds of enums in popovers or properties editors, it's normally just text. I don't think it would look that bad. Icons would not be great either in this kind of layout, they are normally only used in square buttons while these stretch across the width of the panel.

@Pablo Vazquez (pablovazquez) came with the idea to use icons in stead of text? The two line will not always look nice like

Minor implementation detail: there is not enough space to expand enum buttons on one row, we need to spread it out over two rows manually instead of using a slower menu.

We decided to add this for 2.80, also to solve dynamic paint result visualization not working yet.

Archiving in favor of T61578: Outliner Visibility Update, which contains the latest version of the proposed design (to be further updated after discussion at homestretch workshop).

Hrmf, after a bit more digging, I still lack a "proper" solution [at least it feels like that...]

Hm, without having looked at this again (will do on monday), just want to note that the following are all very tighly related:

@Brecht Van Lommel (brecht), i've been looking into the change. Not really sure yet why it is required to do some calculations in original object, and some of them are on both. To me it seems that where_is will return same matrix for both ob and ob_eval?

@Sergey Sharybin (sergey), can you check this?

Or we could prepare the evaluated object as best as we can like so?

@Sergey Sharybin (sergey): Would it make sense to have a version of BKE_object_workob_calc_parent that works strictly with the originals [parent] (since that would fix this bug afaict)?
(Or is this even more inconsistent?)

I've mentioned this library now /shared/info/Animation Studio.odt.

@Clément Foucault (fclem) Doesn't seem to help for me either. The materials still end up pink.

@Julien Kaspar (JulienKaspar) I added a small optimization for rgb curves (rBc49a70bcd113) that could help in this case. Here the material just displays black so I guess it is still not working on my end. But I have a different GPU so you might have better luck.

From @Julien Kaspar (JulienKaspar) on IRC:

Getting an assert:

BLI_assert failed: /home/zed/programmering/blender_master/blender/source/blender/blenkernel/intern/node.c:1741, ntreeFreeLocalNode(), at '(ntree->id.tag & LIB_TAG_LOCALIZED) != 0'