<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>[BUG] GFX line drawing mishandles start/end values</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/37284/bug-gfx-line-drawing-mishandles-start-end-values</link><description>When drawing lines of equal start and end x, y coordinates the GFX library shall draw a rectangle with thickness applied. If the value of the opposing axis has a start value greater than the end value this results in a line drawn in the opposite direction</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 10 Aug 2018 13:01:55 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/37284/bug-gfx-line-drawing-mishandles-start-end-values" /><item><title>RE: [BUG] GFX line drawing mishandles start/end values</title><link>https://devzone.nordicsemi.com/thread/143733?ContentTypeID=1</link><pubDate>Fri, 10 Aug 2018 13:01:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:de4d9ff2-6c4c-4397-9637-7ae44f218974</guid><dc:creator>cxz</dc:creator><description>&lt;p&gt;Thanks Aryan.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: [BUG] GFX line drawing mishandles start/end values</title><link>https://devzone.nordicsemi.com/thread/143724?ContentTypeID=1</link><pubDate>Fri, 10 Aug 2018 12:37:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8d96a51e-2ecc-4473-bcf4-13aa1c1c0f86</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Thanks for letting us know about this.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Your fix seems logical, I will forward this to the team to take a look at and possibly fix it in the next release. For your reference, our internal tracking number for this is&amp;nbsp;NRFFOETT-2083&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>