﻿<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Millisecond Forums » Millisecond Forums » Inquisit 4  » Converting to pixels</title><generator>InstantForum 2017-1 Final</generator><description>Millisecond Forums</description><link>https://forums.millisecond.com/</link><webMaster>Millisecond Forums</webMaster><lastBuildDate>Wed, 08 Apr 2026 09:06:23 GMT</lastBuildDate><ttl>20</ttl><item><title>Converting to pixels</title><link>https://forums.millisecond.com/Topic15002.aspx</link><description>Hi,&amp;nbsp;&lt;br/&gt;&lt;br/&gt;I spent some time figuring out why my dynamic positioning didn't work. In the end I realized this does not work:&amp;nbsp;&lt;br/&gt;&lt;span&gt;[quote]/ position = (900 * 1px, 900 * 1px)[/quote]&lt;/span&gt;&lt;br/&gt;however this does:&lt;br/&gt;&lt;span&gt;[quote]/ position = (1px * 900,1px * 900)[/quote]&lt;br/&gt;&lt;br/&gt;Is there a reason why the order of the components matters?&amp;nbsp;&lt;br/&gt;&lt;br/&gt;Thank you!&lt;br/&gt;&lt;br/&gt;Kerwin&lt;/span&gt;</description><pubDate>Mon, 17 Nov 2014 03:05:33 GMT</pubDate><dc:creator>Kolfers</dc:creator></item><item><title>RE: Converting to pixels</title><link>https://forums.millisecond.com/Topic15004.aspx</link><description>Yes, order matters. The unit of the first term determines the unit of the result:&lt;br/&gt;&lt;br/&gt;1px * 400 -&amp;gt; result will be interpreted as pixels&lt;br/&gt;400 * 1px -&amp;gt; result will&amp;nbsp; be interpreted as pure integer (no unit)&lt;br/&gt;&lt;br/&gt;The reason this matters is that there must be a way to deal with terms with different units. E.g, should 1px * 400pct return a result in pixels or percentages? The order of the terms allows you/ the program to decide that.&lt;br/&gt;</description><pubDate>Mon, 17 Nov 2014 03:05:33 GMT</pubDate><dc:creator>Dave</dc:creator></item></channel></rss>