(in case it's a known limitation would it be acceptable to have the onion skin switch for a layer automatically disable whenever it was added as a mask for another layer?)

thanks! works as expected in the newest alpha

Ah i see. Thanks. perhaps the problem is the tooltip text and name: 'Disable Selection' doesn't imply (to me) that the current selection will be lost (it is).

With the new change, if i have 'Use Factor' turned on, i expected 'start delay' and 'frames' values to be ignored. but currently the animation (driven by the Factor value) only happens within the part of the timeline specified by the 'Frames' and 'Delay' values.

the dope sheet editor's mode selected needs to be changed to 'Grease Pencil' https://docs.blender.org/manual/en/latest/editors/dope_sheet/grease_pencil.html

try opening a dope sheet editor with the grease pencil option selected. your keys should show up there.

Ah! thanks. I had seen this announcement but i overlooked it just now because I didn't have the timeline editor open.

if I have 2 blender windows and I'm using grease pencil what's the recommended way to switch focus without accidentally creating marks?

it seems like it's not specific to the outliner. e.g. when working with pairs of grease pencil frames and clicking (edit mode) interpolate > interpolate on a frame between them. about 20% of the time the default interpolation will be immediately applied. instead of allowing me to interactively set the weight of the interpolation. really frustrating!

I opened the test file in version: 2.91.0, branch: master, commit date: 2020-11-25 08:34, hash: rB0f45cab862b8. I get the same result as in the opening post.

seems it shouldn't be consumed as a double click if the underlying UI element (e.g. a twirl-down toggle) doesn't respond to double clicks. At least this is how all the other UIs i've used work.

here i'm using a mouse.

no i don't. this is the first time i've run blender on a windows machine.

sorry for overlooking the request for more information.

treat brush settings as we do with UI data, or the position of the 3D cursor for example, and ignore any of their changes in undo steps.

yes, i think that's another bug (that you can't set negative frames via the usual number fields)

thanks for clarifying!

thanks, apologies for the noise.

Got it! i don't mind them being visible, can help avoid confusion. Though hidden in render seems like a good idea to me.

I no longer have this problem using the latest build.
2.91.0 Alpha, branch: master, commit date: 2020-08-25 19:28, hash: rB396d39c6b904

I no longer have this problem using:
2.91.0 Alpha, branch: master, commit date: 2020-08-23 12:48, hash: rBe4932d1167f4

I tried the latest blender alpha on both my macbook pro and imac, same problem with both. Pasting system information below in case it's helpful.

i'd be happy to try to find which version breaks this specifically on my machine, but not sure if/how i can get hold of the previous experimental builds.

Additive drawing is by layer, so only the active layer is affected.

The previous version i used (where it works) was rBb522e834ec30, the rB275f1039d22c is a few days later than that. i'm not sure how to download and test intermediate versions. were there more GPencil changes during that time?

@Hans Goudey (HooglyBoogly) I'm not getting this behaviour in firefox. I need to click once to focus the firefox window, only after that can I click buttons in firefox. blender is the only application i've used that works differently.

What is the use case for viewing [intermediate points]?

fwiw i like that the points are visible, but dimmed. i believe this makes it a little easier to understand what's going on (the modifier *is* adding points, which can't be directly edited).

This behaviour is the same in Grease Pencil too (undo changes the active tool and the tool settings). imo it'd be more appropriate & convenient if changes to tools (selected tool and tool settings) were not recorded in the undo stack, or optionally ignored while undoing/redoing.

Yes, I understand. The issue is that this is at odds with how drawn stokes work; the part of the stroke created later is seen as the end. Is there a (non-technical) reason this should be different for strokes extruded from a point?

Thanks for the explanation. that helps me find a workaround for my use case.

A video showing the result i'm getting (see low FPS in material preview mode despite being a very simple scene)