You need enable Sliders. This is disabled by default in all templates except 2D template.

User case for python and custom data could be:

@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.

@Clément Foucault (fclem) I have included the change of Imm drawing to batch drawing.

• Remove Immediate drawing for Dopesheet not grease pencil bars

• Change bar size depending of the icon size

• Remove double loop

• Update bar to round rectangle

• GPencil: Cleanup, remove tmp and is_left variable
• Merge branch 'master' into temp-gpencil-io

• Change to use Vector in object list
• Fix error when exporting several objects

• Change to use Vector in object list
• Fix error when exporting several objects
• Cleanup commented lines

• Merge branch 'master' into temp-gpencil-bar
• Fix problem of bar when Zoom Out to extreme

• Remove fianl message when operation was done
• More code cleanup
• Merge branch 'master' into temp-gpencil-io

I also have removed gpl_current_set/get and the same for gpfand gps

• First round of code cleanup after review
• Second round of code cleanup after review
• Cleanup unneeded variable
• Cleanup code
• Merge branch 'master' into temp-gpencil-io

I have checked and the error is an assert: BLI_assert failed: D:\MyBlender\BlenderDEV\blender\source\blender\blenkernel\intern\icons.cc:743, BKE_icon_id_ensure(), at 'BLI_thread_is_main()'

@Julian Eisel (Severin) Could you check if the code is consistent with what we talk about on the chat? I have added a new function to draw a rectangle ending with arrow shape.

• Use interface DPI

@Falk David (filedescriptor) mybe you can merge this task.

Rebase on master

• GPencil: Fix bug for Fill

IIRC this bug has been fixed in 2.93.

Tip: If for any artist reason, you cannot move the objects, then move only the origin of the cloud object.

Could you try to move your cloud object a little to front. It looks in some angles the position of the objects makes teh drawing engine not able to decide the right z-depth. If I do that in my system, the problem is solved.

Did not test myself, but the fix looks right and logic. The check must be done with evaluated data, not original.

If you enable In Front, the stroke is visible:

@Sam Cogheil (SimplSam) Yes, you are right, it is the same issue.

I have been checking your file and this is a know limitation. Your GP object is very near in front of the cube. When you are drawing, the stroke is not projected (for speed reasons) and when you finish, the stroke is projected and visible. To solve your problem, you have two options: a) move a little your GP object in front or b) Draw on the surface, but then you need to have a full surface on back.

Sorry, I mean parameter not paramater

@Hans Goudey (HooglyBoogly) @Julian Eisel (Severin) I have tested and this bug is not in 2.83. I have not changed anything in the code related to this area, so do you know what can be the problem? Maybe some UI change?

Yes, actually is not supported to use a resolution different of 1.0. The problem is not only in Fill.

@Hans Goudey (HooglyBoogly) This is my first time using C ++ in Blender. I'm used to object-oriented programming languages, but not C ++, so could you do a quick check on the style of the code?

This error was introduced with commit 1e55d28a4e24 in task T85035.

Right, this is not supported. It's the same with active vertex, not supported yet.

@Jamell Moore (JamellMoore) Don't worry... only those who do something can make a mistake. Thanks for your help fixing the bug.