WIP: GPv3: Geometry-based Fill tool #114318
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#114318
Loading…
Reference in New Issue
No description provided.
Delete Branch "SietseB/blender:gp3-vector-fill"
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?
Work in progress
This is an experimental attempt to implement a vector-based Fill tool
for GPv3. Vector-based means: using the actual points of the edge
strokes, instead of creating new, unrelated geometry points as the
GPv2 flood-fill algorithm does.
@antoniov I added some notes to give you a starting point for exploring the 'gap closure' code I used for the Fill tool.
@ -0,0 +3266,4 @@
}
/* Convert curves to viewport 2D space. */
vf->curves_2d = curves_in_2d_space_get(&vf->vc, vf->vc.obact, drawings, layer_indices, true);
Here a set of GP drawings (layers) is converted to viewport 2D space. The function is declared in
editors\include\ED_grease_pencil.hh
and defined ineditors\grease_pencil\intern\grease_pencil_utils.cc
.In the
curves_2d
structure all curves of all layers are packed together and accessible through offset indices. E.g. looping over all first and last points of all curves goes this way:Relevant functions for gap closure by stroke end radius are:
init_curve_end_radii()
get_connected_curve_end_radii()
For gap closure by extending the stroke ends:
init_curve_end_extensions()
get_curve_end_extensions()
The drawing of the gap lines in the viewport is done in:
draw_overlay()
I'm just scanning over the code to get an initial idea. Looks like you put a lot of thought into this!
One thing that I'm seeing is that you're using
float2
for your 2d coordinates. And I can see that you're also having to do lots and lots of epsilon checks because of the precision issues.Since we're already in screen space, I would advise to use
int2
for the coordinates instead. That allows for precise intersection checks, without having to deal with floating point arithmetic.Amelie ended up taking that same route for the eraser.
WIP: GPv3: Vector-based Fill toolto WIP: GPv3: Geometry-based Fill toolCheckout
From your project repository, check out a new branch and test the changes.