<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with qgraphicspath]]></title><description><![CDATA[A list of topics that have been tagged with qgraphicspath]]></description><link>https://forum.qt.io/tags/qgraphicspath</link><generator>RSS for Node</generator><lastBuildDate>Thu, 01 Oct 2026 03:58:24 GMT</lastBuildDate><atom:link href="https://forum.qt.io/tags/qgraphicspath.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[QGraphicsView, QGraphicsPath - find closest path ?]]></title><description><![CDATA[Also another problem with path.contains that I find is that the contains would use this as check area &gt;
https://doc.qt.io/archives/qt-4.8/images/graphicsview-pathitem.png
Which means that the shape can be bigger/inaccurate comparing to the selection location... I think I will need to do some math and create another method for path click intersection.
Ok I sorta managed to "fix" it... I ended up creating a forward and then reverse path during selection process. So that the path is a closed - precise - shape. This way I can get proper click detection, I still cant compute which path is closer, but at least selection works properly now.
]]></description><link>https://forum.qt.io/topic/108105/qgraphicsview-qgraphicspath-find-closest-path</link><guid isPermaLink="true">https://forum.qt.io/topic/108105/qgraphicsview-qgraphicspath-find-closest-path</guid><dc:creator><![CDATA[Dariusz]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>