<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Unorthodox checkbox usage	</title>
	<atom:link href="https://undocumentedmatlab.com/articles/unorthodox-checkbox-usage/feed" rel="self" type="application/rss+xml" />
	<link>https://undocumentedmatlab.com/articles/unorthodox-checkbox-usage?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=unorthodox-checkbox-usage</link>
	<description>Professional Matlab consulting, development and training</description>
	<lastBuildDate>Wed, 04 Feb 2015 15:41:22 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.7.3</generator>
	<item>
		<title>
		By: David Sampson		</title>
		<link>https://undocumentedmatlab.com/articles/unorthodox-checkbox-usage#comment-345223</link>

		<dc:creator><![CDATA[David Sampson]]></dc:creator>
		<pubDate>Wed, 04 Feb 2015 15:41:22 +0000</pubDate>
		<guid isPermaLink="false">http://undocumentedmatlab.com/?p=5457#comment-345223</guid>

					<description><![CDATA[Thanks for the comments and I&#039;m glad that you benefited from studying the GUI Layout Toolbox code.

Yes GLT was a rewrite for our code but we worked hard to make sure it wasn&#039;t a rewrite for your code.  Package &lt;code&gt;uiextras&lt;/code&gt; in GLT2 is a compatibility layer to provide support for code that you wrote prior to 14b.  User feedback and testing across MathWorks Consulting&#039;s portfolio of customer applications built on GLT suggests that migration effort is none or minor.  Nevertheless, if you have problems or suggestions, please get in touch via File Exchange comments.

We wanted to make GLT2 containers real graphics objects (inheritance rather than composition) to enable highly readable code like &lt;code&gt;child.Parent = gltContainer&lt;/code&gt;.  However such inheritance wasn&#039;t feasible in HG1, hence the separate downloads for HG1 and HG2.

Finally we revisited the GLT APIs for HG2 and wanted to make some minor changes to property names to improve consistency and ease-of-learning.  These are confined to a new package &lt;code&gt;uix&lt;/code&gt;, and we recommend that you use this for new code that doesn&#039;t have to run prior to 14b.  Don&#039;t bother migrating pre-14b code to &lt;code&gt;uix&lt;/code&gt;, and you need to use &lt;code&gt;uiextras&lt;/code&gt; if you want your code to run both pre- and post-14b.]]></description>
			<content:encoded><![CDATA[<p>Thanks for the comments and I&#8217;m glad that you benefited from studying the GUI Layout Toolbox code.</p>
<p>Yes GLT was a rewrite for our code but we worked hard to make sure it wasn&#8217;t a rewrite for your code.  Package <code>uiextras</code> in GLT2 is a compatibility layer to provide support for code that you wrote prior to 14b.  User feedback and testing across MathWorks Consulting&#8217;s portfolio of customer applications built on GLT suggests that migration effort is none or minor.  Nevertheless, if you have problems or suggestions, please get in touch via File Exchange comments.</p>
<p>We wanted to make GLT2 containers real graphics objects (inheritance rather than composition) to enable highly readable code like <code>child.Parent = gltContainer</code>.  However such inheritance wasn&#8217;t feasible in HG1, hence the separate downloads for HG1 and HG2.</p>
<p>Finally we revisited the GLT APIs for HG2 and wanted to make some minor changes to property names to improve consistency and ease-of-learning.  These are confined to a new package <code>uix</code>, and we recommend that you use this for new code that doesn&#8217;t have to run prior to 14b.  Don&#8217;t bother migrating pre-14b code to <code>uix</code>, and you need to use <code>uiextras</code> if you want your code to run both pre- and post-14b.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
