thanks! i don't get the crash in the latest build.

@Richard Antalik (ISS) yes. i still get the crash after i load the factory settings.

and the crash text

here they are

@Matias Mendiola (mendio) see my replies inline re. the suggestions.

at @Matias Mendiola (mendio)'s suggestion edited the revision to just include an image of the properties editor as a clue for where to find the curve widgets.
not sure if the image is embedded in this diff so i'll upload again and attach.

Thanks for the clarification! i'll close the ticket if everyone's ok with that

ah thank you! that makes sense.

For anyone else experiencing this: opening a new file and appending the scene from the broken .blend allowed me to continue working. the bug didn't persist in the new file.

I couldn't recreate the problem with the latest alpha :D
3.0.0 Alpha, branch: master, commit date: 2021-05-16 05:49, hash: rB0e581f619670

hmm. That's odd. Just to check: In other apps the pressure seems to be polling correctly even while the stylus is still. Here's Krita:

ah i guess it might be a windows problem then. Here's a video of my screen. For each dot i was touching the stylus to the surface, gradually increasing pressure, then taking the tip off the surface.

@Falk David (filedescriptor) thanks! i've applied the patch.

@Falk David (filedescriptor) would love to test this! but i'm not sure how to apply it to my local repository. First time trying to apply a patch, going wrong somewhere.

that was exactly my suggestion 🙂

sorry for the ambiguous image. the red line on the left is an annotation on the screenshot to call out the position of the unwanted line.

whether using wintab or windows ink i get unwanted artefacts.

ah thanks. i guess i'd gotten lucky before, didn't notice this difficulty.

(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). ie. 'Disable Selection' != 'Deselect'.

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.