LGTM

IMO, this is the wrong approach.

@William Reynish (billrey): Looks good. By and large, what you've got there makes sense - I particularly agree that we do want these different draw styles to be able to be turned on/off as needed; indeed it's something that some of the earlier mockups really drove home.

@Samir Osman (Samirosman): That's looking promising. However, as per my previous comments, it's unclear with some of these what frame exactly those things sit on. The arrow like ones are particularly bad in this regard, but to a lesser extent the square (constant) and circle are also not great.

@William Reynish (billrey) Nice idea. Personally, numbers 1 & 2 are the more promising ones there - on an aesthetic level, I like 1 more, but 2 probably communicates what's going on better (as the gradients make subtle differences harder to see). The only potential issue here is regarding performance, but as long as we don't care too much about accurately representing the transition between the keyframes (i.e. no sampling of the curves to find out what's going on, and just using some prebaked effects in fragment shaders) I think we can do it (in which case, 1 is actually more convenient to implement).

1. Looking it again today, I still have serious doubts about the legibility of these markings. They are almost impossible to distinguish and it's also hard to understand what exactly each symbol is trying to convey.

Thanks for the report. This is a known limitation that we've been trying to resolve for a few months now, due to some keymap conflicts. IIRC, we actually have a task open for this already - see T55420

Please follow our submission template and guidelines and make a complete, valid bug report,
with required info, precise description of the issue, precise steps to reproduce it,
small and simple .blend and/or other files to do so if needed, etc.

Note: Just confirmed that this is still happening in HEAD (4f06c7c8389d144394efdda8829f3d01283694d6)

@Clément Foucault (fclem) Assigning to our resident draw engine guru :)

@Charlie Jolly (charlie) Thanks, looks like an easy fix.

Note - rB939a5cb6eec adds the toolbar button for the Annotation tool, but for reasons currently unknown, the events don't seem to get fired correctly here.

Cannot reproduce (Win10, GTX1080Ti, 76ea32d192693ac0d46270dd30c7e50a0bfcea62)

Closing. I fixed it in another, much better way.

@Clément Foucault (fclem) Yep, this solves the crash here. UI draws normally, and Spring files can be loaded.

@Konstantin Bukow (Kobuk) Short of modifying the grease pencil code (see gpencil_draw_modal() in either gpencil_paint.c or annotate_paint.c) to check what pressure values Blender is getting/using, you could also try running Blender with the --debug-events flag.

Can you reproduce on the default scene (cube + camera + lamp)? If not, you have probably locked selection (check outliner, cursor icons column) on one or more objects.

Not a bug. Deselect is now Alt-A

I couldn't reproduce this issue, but I think I know what may cause it (I still don't know how exactly it gets triggered though).

Please follow our submission template and guidelines and make a complete, valid bug report,
with required info, precise description of the issue, precise steps to reproduce it,
small and simple .blend and/or other files to do so if needed, etc.

Please follow our submission template and guidelines and make a complete, valid bug report,
with required info, precise description of the issue, precise steps to reproduce it,
small and simple .blend and/or other files to do so if needed, etc.

Please follow our submission template and guidelines and make a complete, valid bug report,
with required info, precise description of the issue, precise steps to reproduce it,
small and simple .blend and/or other files to do so if needed, etc.

Yes, these are known limitations that are tied fairly deeply into Blender's data structures and infrastructure, from when it was designed in the early 90's.

Sure - that's actually on my todo, along with a bunch of other things like that.

Initially I thought so too - hence why I originally omitted it (and actually, it's simpler without it being there).

Actually, most of the shape operators could and should just become active tools. Especially the rect/circle ones. Monkey though isn't interactive so should just be left for the Add menu

Is this with master/2.7 or 2.8?