The 2.83 has a total redesign of the system and this parameter has been removed.

The slider are not visible for annotations and this datablock is set as annotation:

To change to RGBA instead to RGB could have impact in GPencil because the Alpha is not used and depends of other parameters. To keep GPencil running we would need to have in RNA a prop with 3 (RGB) to avoid the UI displays the Alpha channel selector. Also need some small adjustment in the paint code, but nothing big.

The reason to had different code was the modifier was initially totally different and never was cleanup.

@Andry (dedouze) Did you find a way to reproduce it? have you found again the bug?

All compiler issues have gone. I have tested and all looks right. Now if you have several panels with the same FX, all are updated.

Fixed, Thanks @Clément Foucault (fclem) for finding the root cause.

@Jeroen Bakker (jbakker) This one for 2.83.2

@Jeroen Bakker (jbakker) This one is good for 2.83.2

I can confirm on Windows with NVIDIA card.

I cannot replicate on Windows 10 RTX2080TI

@Clément Foucault (fclem) @Brecht Van Lommel (brecht) Thoughts?

The code looks good to me, but I could not compile due the duplicated case error.

• GPencil: Fix errors after merge

LGTM

So, if you can draw with the mouse means that the tablet driver is not working.

Can you draw using the mouse? This problem looks related to the pen driver or something like that.

Sorry for that... in Windows withj MSVS compiles perfect.

• Cleanup code

Please check D8141

Crash Fixed!

As the merge by distance is also available, following the policy of this web I have to close the report because it cannot be consider as a bug.

This is by design and have not changed since a lot of versions. When you pass the circle over, you are selecting the stroke, not only the point. We could do in the way you explain, but it would a change of how is working for years. I don't mean your proposal will be worse or better, just a different approach to the problem.

The problem is the merge operator does not mean the same as in Meshes. The merge take several points and merge all together to create a new stroke. The merge you want is more the Dissolve of GPencil.

This is not a bug. Merge points only works in the same stroke. If you want join two stroke use the Join operator.

I have made a change in the extraction of color. Now the threshold has been removed because after doing tests, using a number greater than 1 was not a good solution. See commit fec2b2a809a8

After doing test with the palettes, use a threshold greater than 1 has no sense because the number of generated colors is hue. When the thershold is greater than one, any slightly variation in the tone of the color produces a new palette entry,

It looks the size of the popover panel is too big. I think is better limit the size of the palette.

Crash log

!__chkstk() Line 109	Unknown
!ui_block_align_calc(uiBlock * block, const ARegion * region) Line 439	C
!UI_block_end_ex(const bContext * C, uiBlock * block, const int * xy, int * r_xy) Line 1779	C
!ui_popup_block_refresh(bContext * C, uiPopupBlockHandle * handle, ARegion * butregion, uiBut * but) Line 637	C
!ui_popup_block_create(bContext * C, ARegion * butregion, uiBut * but, uiBlock *(*)(bContext *, ARegion *, void *) create_func, uiBlock *(*)(bContext *, uiPopupBlockHandle *, void *) handle_create_func, void * arg, void(*)(void *) arg_free) Line 832	C
!ui_popover_panel_create(bContext * C, ARegion * butregion, uiBut * but, void(*)(bContext *, uiLayout *, void *) menu_func, void * arg) Line 279	C
!ui_block_open_begin(bContext * C, uiBut * but, uiHandleButtonData * data) Line 4040	C
!button_activate_state(bContext * C, uiBut * but, uiHandleButtonState state) Line 7939	C
!ui_do_but_COLOR(bContext * C, uiBut * but, uiHandleButtonData * data, const wmEvent * event) Line 5855	C
!ui_do_button(bContext * C, uiBlock * block, uiBut * but, const wmEvent * event) Line 7611	C
!ui_handle_button_event(bContext * C, const wmEvent * event, uiBut * but) Line 8873	C
!ui_region_handler(bContext * C, const wmEvent * event, void * UNUSED_userdata) Line 10685	C
!wm_handler_ui_call(bContext * C, wmEventHandler_UI * handler, const wmEvent * event, int always_pass) Line 622	C
!wm_handlers_do_intern(bContext * C, wmEvent * event, ListBase * handlers) Line 2743	C
!wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 2854	C
!wm_event_do_handlers(bContext * C) Line 3357	C
!WM_main(bContext * C) Line 478	C
!main(int argc, const unsigned char * * UNUSED_argv_c) Line 534	C
 	[External Code]

This is not a bug. In your file, the edge of the stroke has only two points and when you put in some angles the stroke is clamped due the size of the edge. To solve, just subdivide the stroke and add more geometry and you can rotate without problem.

I cannot reproduce it. In the video the scale is not 1.0, but it works fine with any scale.

This report does not contain all the requested information, which is required for us to investigate the issue.