GPv3: Fill tool #120693
No reviewers
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#120693
Loading…
Reference in New Issue
No description provided.
Delete Branch "LukasTonne/blender:gp3-fill-tool"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implementation of the GPv2 Fill tool in Grease Pencil 3.
UI
Algorithm
DrawingPlacement
)Features to add later (not in this PR)
ed::greasepencil::image_render::draw_dots
)As a clarification of the gap closure methods – there are three ways:
Alt-LMB
.I know it's just WIP yet, but I wanted to mention that multi frame editing complicates things a bit.
In the example above, with multi frame editing enabled, the fill tool should be executed three times: for frame 1, 5 and 10. So the drawings should be retrieved grouped per frame number.
I mention it now, because it might influence how you organize your data. The boundary layers, for example, can differ per group. And the collisions of extend lines also need to be calculated per group.
@ -439,0 +640,4 @@
/* Drawings that form boundaries for the generated strokes. */
const Vector<DrawingInfo> src_drawings = ed::greasepencil::retrieve_visible_drawings(
scene, grease_pencil, false);
To handle multi frame editing, the drawings must be retrieved grouped by frame number.
I don't think there is a good utility function for this specific case yet (and it's so special that i don't think adding one is justified). I'll do this locally for the operator:
retrieve_editable_drawings_grouped_per_frame
is close, but i only want the drawing from the active layer, otherwise the same boundary strokes would get added to all the layers.retrieve_visible_drawings
does not group drawings by frame which is probably desirable, otherwise the result would again be the same in every frame.Thank you @SietseB for the explanation!
I'll try to structure the code in such a way that the different stages of the tool are more clearly separated. The GPv2 tool is using the same
tGPDfill
struct for every single function, which makes it hard to tell which data is relevant for which part of the process.283cc6e221
to0c92c70c99
WIP: GPv3: Fill toolto GPv3: Fill tool40c4b1400a
to5a89d4226c
@blender-bot package
Package build started. Download here when ready.
Checkout
From your project repository, check out a new branch and test the changes.