0001934: A specific path does not result in anti-aliasing being applied

ID	Project	Category	View Status	Date Submitted	Last Update

0001934	NoesisGUI	C# SDK	public	2021-03-05 15:07	2025-08-06 17:11

Reporter	darthmaule2	Assigned To	jsantos
Priority	normal	Severity	minor
Status	resolved	Resolution	fixed
Product Version	3.0.10
Fixed in Version	3.2.8

Summary	0001934: A specific path does not result in anti-aliasing being applied
Description	This path results in obvious jagged edges. <Path Data="M0 0 L16 32 L0 64 L16 64 L16 0 Z"/> But a slightly modified shape can be used as a work-around so this is low priority <Path Data="M0 0 L15 32 L0 64 L16 64 L16 0 Z"/>

Platform	Any

Date Modified	Username	Field	Change
2021-03-05 15:07	darthmaule2	New Issue
2021-03-08 16:58	sfernandez	Assigned To	=> sfernandez
2021-03-08 16:58	sfernandez	Status	new => assigned
2021-03-08 16:59	sfernandez	Assigned To	sfernandez => jsantos
2021-03-08 16:59	sfernandez	Target Version	=> 3.0.11
2021-03-12 10:53	jsantos	Note Added: 0007073
2021-03-12 10:54	jsantos	Target Version	3.0.11 =>
2021-03-12 18:35	sfernandez	Target Version	=> 3.0.11
2021-03-13 20:35	jsantos	Target Version	3.0.11 =>
2025-08-06 17:11	sfernandez	Status	assigned => resolved
2025-08-06 17:11	sfernandez	Resolution	open => fixed
2025-08-06 17:11	sfernandez	Fixed in Version	=> 3.2.8

jsantos 2021-03-12 10:53 manager ~0007073	This is a hard case for our PPAA (cheap antialiasing) algorithm because the tessellator is generating two triangles that share a vertex. That vertex has 4 connected edges and the averaged normal used for PPAA is not correct. There is no easy solution for this without having a slower algorithm. I need to think more about it.