{"push_id":1737467453,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"074197580595e06936fbb830069103d66c7c65db","before":"1dcbe6769c7ba0abde1f4b7c312441568033dab2","commits":[{"sha":"074197580595e06936fbb830069103d66c7c65db","author":{"name":"Tanner","email":"43881d0eebaaa2a73a01dc88167c8c69868ed637@tannerhelland.com"},"message":"Flood fill: performance and quality improvements\n\nI'm working on a true scanline floodfill implementation (as opposed to\nthe simplified \"test run\" version in this commit), but early results are\npromising.  It's the sheer volume of edge cases that make a \"perfect\"\nresult bothersome.\n\nIn the meantime, polygon rendering is now used to populate the\ndestination \"fill DIB\", which shaves precious time off the actual flood\nfill (because all we do in that step is populate the fill map - which\nmeans we're no longer bouncing around in memory due to destination DIB\naccesses).  A vector approach means that we get true, \"perfect\"\nantialiasing along wand selection edges, as opposed to a raster-based\n\"estimation\" like the old function.  This yields meaningful performance\nand quality improvements, so wins all around.","distinct":true,"url":"https://api.github.com/repos/tannerhelland/PhotoDemon/commits/074197580595e06936fbb830069103d66c7c65db"}]}
{"actor":{"display_login":"tannerhelland"}}