<?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"
	>
<channel>
	<title>Comments on: In Place Element Strucure - Saves Time and Prevents Bugs</title>
	<atom:link href="http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/feed/" rel="self" type="application/rss+xml" />
	<link>http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/</link>
	<description>an unfiltered stream of data flow consciousness</description>
	<pubDate>Fri,  5 Sep 2008 20:09:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Jim Kring</title>
		<link>http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4841</link>
		<dc:creator>Jim Kring</dc:creator>
		<pubDate>Wed, 06 Feb 2008 17:11:22 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4841</guid>
		<description>Patrick: That looks like a nasty bug.  Thanks for link.</description>
		<content:encoded><![CDATA[<p>Patrick: That looks like a nasty bug.  Thanks for link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Lavezza</title>
		<link>http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4811</link>
		<dc:creator>Patrick Lavezza</dc:creator>
		<pubDate>Wed, 06 Feb 2008 05:50:45 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4811</guid>
		<description>Sorry, I messed up the &lt;a href="http://forums.ni.com/ni/board/message?board.id=170&#38;message.id=299880#M299880" rel="nofollow"&gt;link&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Sorry, I messed up the <a href="http://forums.ni.com/ni/board/message?board.id=170&amp;message.id=299880#M299880" rel="nofollow">link</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Lavezza</title>
		<link>http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4810</link>
		<dc:creator>Patrick Lavezza</dc:creator>
		<pubDate>Wed, 06 Feb 2008 05:49:49 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4810</guid>
		<description>Someone just posted this &lt;a href="http://forums.ni.com/ni/board/messageboard.id=170&#38;message.id=299880#M299880" rel="nofollow"&gt;bug&lt;/a&gt; to NI's forums.</description>
		<content:encoded><![CDATA[<p>Someone just posted this <a href="http://forums.ni.com/ni/board/messageboard.id=170&amp;message.id=299880#M299880" rel="nofollow">bug</a> to NI&#8217;s forums.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Kring</title>
		<link>http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4776</link>
		<dc:creator>Jim Kring</dc:creator>
		<pubDate>Tue, 05 Feb 2008 17:20:58 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4776</guid>
		<description>Chris: I've made the images local.  You should now be able to see them.</description>
		<content:encoded><![CDATA[<p>Chris: I&#8217;ve made the images local.  You should now be able to see them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Davis</title>
		<link>http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4727</link>
		<dc:creator>Chris Davis</dc:creator>
		<pubDate>Mon, 04 Feb 2008 19:41:54 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4727</guid>
		<description>Jim,
I haven't tried it myself yet, but I think this proves that flickr is blocked by my IT department.  Thanks for your blog.</description>
		<content:encoded><![CDATA[<p>Jim,<br />
I haven&#8217;t tried it myself yet, but I think this proves that flickr is blocked by my IT department.  Thanks for your blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Kring</title>
		<link>http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4588</link>
		<dc:creator>Jim Kring</dc:creator>
		<pubDate>Fri, 01 Feb 2008 17:40:51 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4588</guid>
		<description>Chris: I did something a little different with the images, this time.  I hosted them on Flickr.  Is flickr.com blacklisted by your IT dept?</description>
		<content:encoded><![CDATA[<p>Chris: I did something a little different with the images, this time.  I hosted them on Flickr.  Is flickr.com blacklisted by your IT dept?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Davis</title>
		<link>http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4586</link>
		<dc:creator>Chris Davis</dc:creator>
		<pubDate>Fri, 01 Feb 2008 12:29:25 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4586</guid>
		<description>Jim,
     I can't see the code snippet images you've put in your blog.  I've tried IE7 and Firefox 2, but it could still be something on my end.  I'm assuming everyone else can see them right?</description>
		<content:encoded><![CDATA[<p>Jim,<br />
     I can&#8217;t see the code snippet images you&#8217;ve put in your blog.  I&#8217;ve tried IE7 and Firefox 2, but it could still be something on my end.  I&#8217;m assuming everyone else can see them right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Holt</title>
		<link>http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4480</link>
		<dc:creator>Matt Holt</dc:creator>
		<pubDate>Wed, 30 Jan 2008 16:54:10 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4480</guid>
		<description>-- Rant on --
I agree with Mr. Aivaliotis, NI doesn't recruit from Industry enough for the dev teams to have any real knowledge of how the average user interacts with the software.
-- Rant off --

I put the memory control sub palette on the structures palette, not a great solution, but at least the structure is accessible this way. It would be great if we had the ability to fully customize the palettes versus just adding other palettes and VIs.... as in, copy the link from the memory control palette to the structures palette at our choosing.</description>
		<content:encoded><![CDATA[<p>&#8211; Rant on &#8211;<br />
I agree with Mr. Aivaliotis, NI doesn&#8217;t recruit from Industry enough for the dev teams to have any real knowledge of how the average user interacts with the software.<br />
&#8211; Rant off &#8211;</p>
<p>I put the memory control sub palette on the structures palette, not a great solution, but at least the structure is accessible this way. It would be great if we had the ability to fully customize the palettes versus just adding other palettes and VIs&#8230;. as in, copy the link from the memory control palette to the structures palette at our choosing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Aivaliotis</title>
		<link>http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4458</link>
		<dc:creator>Michael Aivaliotis</dc:creator>
		<pubDate>Wed, 30 Jan 2008 09:25:07 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4458</guid>
		<description>Why can't it be in both locations? In the Memory Control palette AND the structures palette?
In any case NI yet again seems to be out of touch with how the typical user "uses" the LabVIEW environment.</description>
		<content:encoded><![CDATA[<p>Why can&#8217;t it be in both locations? In the Memory Control palette AND the structures palette?<br />
In any case NI yet again seems to be out of touch with how the typical user &#8220;uses&#8221; the LabVIEW environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen</title>
		<link>http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4421</link>
		<dc:creator>Stephen</dc:creator>
		<pubDate>Tue, 29 Jan 2008 17:37:08 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/01/29/in-place-element-strucure-saves-time-and-prevents-bugs/#comment-4421</guid>
		<description>In the future, there will be more structures that are not in the "Structures" palette. This palette has turned out to be a bad idea as structures are added that relate to specific aspects of LabVIEW. The general "flow of control" structures will remain where they are, but others may appear in palettes specific to their purposes. The Inplace Element Structure is merely the first of these. 

As always, the phrase "in the future" has no bounding when I use it to describe LabVIEW, and you may not see anything along these lines for many years.</description>
		<content:encoded><![CDATA[<p>In the future, there will be more structures that are not in the &#8220;Structures&#8221; palette. This palette has turned out to be a bad idea as structures are added that relate to specific aspects of LabVIEW. The general &#8220;flow of control&#8221; structures will remain where they are, but others may appear in palettes specific to their purposes. The Inplace Element Structure is merely the first of these. </p>
<p>As always, the phrase &#8220;in the future&#8221; has no bounding when I use it to describe LabVIEW, and you may not see anything along these lines for many years.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
