GPencil: Material Hidden/Locked still receives inputs. #115324

New Issue

adam · 2023-11-24T02:29:26+01:00

adam commented

2023-11-24 02:29:26 +01:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 750/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23

Blender Version
Broken: version: 4.0.0, branch: blender-v4.0-release, commit date: 2023-11-13 17:26, hash: 878f71061b8e.
-Also occurred in Blender 3.6.

Short description of error
When Locking or Hiding a GP material, I can still perform operations (Copy, Paste, Automerge) on a stroke with that material.

Exact steps for others to reproduce the error
There are 2 materials: Mat1 is Unlocked/Visible, Mat2 will be Locked/Hidden.

Issue 1A: Automerge On, Mat2-Locked, drawing a Mat1-Stroke over Mat2 still merges.
Issue 1B: Automerge On, Mat2-Hidden, drawing a Mat1-Stroke over Mat2 still merges, and stroke disappears.

Note: If Automerge On, Mat1-Locked, Mat2-Unlocked, then drawing a Mat1-Stroke over Mat2 doesn't merge (as expected). But the expectation is any locked/hidden material wouldn't receive edits/inputs.

Issue 2A: If Mat2-Stroke is selected, then Locked, the selection is still active, so if you select a Mat1-Stroke, Copy+Paste, it also copied the Mat2-Stroke and there is a duplicate unexpectedly on top of it.
Issue 2B: If Mat2-Stroke is selected, then Hidden, you can see the wireframe of selection, but can't de-select until you Unhide the material (which you might not know if there are a lot of materials).

Technically, Material-Locking is supposed to prevent edits, meaning it can also be used to prevent editing 'saved selections', but I'm thinking it might avoid confusion if protecting selections were exclusive to Vertex Groups.

Apologies if this should be in multiple reports.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 750/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23 **Blender Version** Broken: version: 4.0.0, branch: blender-v4.0-release, commit date: 2023-11-13 17:26, hash: `878f71061b8e`. -Also occurred in Blender 3.6. **Short description of error** When Locking or Hiding a GP material, I can still perform operations (Copy, Paste, Automerge) on a stroke with that material. **Exact steps for others to reproduce the error** There are 2 materials: Mat1 is Unlocked/Visible, Mat2 will be Locked/Hidden. - Issue 1A: Automerge On, Mat2-Locked, drawing a Mat1-Stroke over Mat2 still merges. - Issue 1B: Automerge On, Mat2-Hidden, drawing a Mat1-Stroke over Mat2 still merges, and stroke disappears. Note: If Automerge On, Mat1-Locked, Mat2-Unlocked, then drawing a Mat1-Stroke over Mat2 doesn't merge (as expected). But the expectation is any locked/hidden material wouldn't receive edits/inputs. - Issue 2A: If Mat2-Stroke is selected, then Locked, the selection is still active, so if you select a Mat1-Stroke, Copy+Paste, it also copied the Mat2-Stroke and there is a duplicate unexpectedly on top of it. - Issue 2B: If Mat2-Stroke is selected, then Hidden, you can see the wireframe of selection, but can't de-select until you Unhide the material (which you might not know if there are a lot of materials). Technically, Material-Locking is supposed to prevent edits, meaning it can also be used to prevent editing 'saved selections', but I'm thinking it might avoid confusion if protecting selections were exclusive to Vertex Groups. Apologies if this should be in multiple reports.

adam added the

labels 2023-11-24 02:29:26 +01:00

Richard Antalik commented

2023-11-24 05:03:55 +01:00

Since this is implemented as lock of all strokes using the material on user level will confirm.

Richard Antalik added