<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/wordpress-mu-1.2.3-2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: April 2008 Hotfix is Available</title>
	<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050</link>
	<description>The Blog of the Delphi Product Manager</description>
	<pubDate>Fri, 04 Jul 2008 20:35:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=wordpress-mu-1.2.3-2.2.1</generator>

	<item>
		<title>By: Jeff C.</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19561</link>
		<author>Jeff C.</author>
		<pubDate>Thu, 01 May 2008 18:28:38 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19561</guid>
		<description>I often refer friends to download the trial to get a feel for Delphi.  I always wonder when I see these announcements if the trial versions get the same attention, that is, get slipstreamed soon after with the same hotfixes and help updates.

I would hate that a potential customer is turned away by a bug that happens to already be fixed.</description>
		<content:encoded><![CDATA[<p>I often refer friends to download the trial to get a feel for Delphi.  I always wonder when I see these announcements if the trial versions get the same attention, that is, get slipstreamed soon after with the same hotfixes and help updates.</p>
<p>I would hate that a potential customer is turned away by a bug that happens to already be fixed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19524</link>
		<author>David</author>
		<pubDate>Mon, 28 Apr 2008 01:11:05 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19524</guid>
		<description>I personally am happy to see CodeGear's commitment to fixing bugs and improving the help system. I have had fewer problems updating Delphi 2007 than many of my other expensive tool sets :)</description>
		<content:encoded><![CDATA[<p>I personally am happy to see CodeGear&#8217;s commitment to fixing bugs and improving the help system. I have had fewer problems updating Delphi 2007 than many of my other expensive tool sets <img src='http://blogs.codegear.com/nickhodges/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Randall</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19507</link>
		<author>Ken Randall</author>
		<pubDate>Fri, 25 Apr 2008 16:55:51 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19507</guid>
		<description>Works fine fr me but surely this could have been handled much better!</description>
		<content:encoded><![CDATA[<p>Works fine fr me but surely this could have been handled much better!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Hodges</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19483</link>
		<author>Nick Hodges</author>
		<pubDate>Wed, 23 Apr 2008 16:57:21 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19483</guid>
		<description>Rich --

It was a Delphi compiler issue that effected the C++ compiler.  Because the VCL is written in Delphi, and the C++Builder compiler has to consume the results of the Delphi compiler, the two are interrelated.  In this case, the Delphi compiler was incorrectly generating code that effected the C++ compiler.  That has been fixed.

Nick</description>
		<content:encoded><![CDATA[<p>Rich &#8211;</p>
<p>It was a Delphi compiler issue that effected the C++ compiler.  Because the VCL is written in Delphi, and the C++Builder compiler has to consume the results of the Delphi compiler, the two are interrelated.  In this case, the Delphi compiler was incorrectly generating code that effected the C++ compiler.  That has been fixed.</p>
<p>Nick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Werning</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19482</link>
		<author>Rich Werning</author>
		<pubDate>Wed, 23 Apr 2008 15:21:51 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19482</guid>
		<description>#4 says that it's a Delphi compiler issue, but the QC entry says thats it's a C++ compiler issue.  And the QC #57300 is still open, so I'm guessing that there was a mistake made there somewhere.</description>
		<content:encoded><![CDATA[<p>#4 says that it&#8217;s a Delphi compiler issue, but the QC entry says thats it&#8217;s a C++ compiler issue.  And the QC #57300 is still open, so I&#8217;m guessing that there was a mistake made there somewhere.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Hodges</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19481</link>
		<author>Nick Hodges</author>
		<pubDate>Wed, 23 Apr 2008 00:27:02 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19481</guid>
		<description>Rich -

"Which one is it?" 

Which one is what?  Not sure what you are asking.

Nick</description>
		<content:encoded><![CDATA[<p>Rich -</p>
<p>"Which one is it?" </p>
<p>Which one is what?  Not sure what you are asking.</p>
<p>Nick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Werning</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19479</link>
		<author>Rich Werning</author>
		<pubDate>Tue, 22 Apr 2008 18:15:20 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19479</guid>
		<description>Holy cow.. umm, is there a way to get more details on issue #7 since there isn't a QC issue listed with it?  I've been fighting a problem for many months now regarding crashes/hangs with DLL's, which is more pronounced when you're on a multicore machine.  I wonder if that is related to the hotfix issue you've taken care of.</description>
		<content:encoded><![CDATA[<p>Holy cow.. umm, is there a way to get more details on issue #7 since there isn&#8217;t a QC issue listed with it?  I&#8217;ve been fighting a problem for many months now regarding crashes/hangs with DLL&#8217;s, which is more pronounced when you&#8217;re on a multicore machine.  I wonder if that is related to the hotfix issue you&#8217;ve taken care of.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Werning</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19478</link>
		<author>Rich Werning</author>
		<pubDate>Tue, 22 Apr 2008 18:07:02 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19478</guid>
		<description>Reading the hotfix list, #4 states "Delphi Win32 compiler generates misaligned data structures causing AV", but when you look at the QC it references - 57300 - it's still flagged as being open and that it applies to the C++ compiler.  Which one is it?</description>
		<content:encoded><![CDATA[<p>Reading the hotfix list, #4 states "Delphi Win32 compiler generates misaligned data structures causing AV", but when you look at the QC it references - 57300 - it&#8217;s still flagged as being open and that it applies to the C++ compiler.  Which one is it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Hodges</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19477</link>
		<author>Nick Hodges</author>
		<pubDate>Tue, 22 Apr 2008 17:38:08 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19477</guid>
		<description>Robert --

Here is what I'd do:

1.  Run a repair
2.  Install the December update
3.  Re-run the Hotfix installer.

Nick</description>
		<content:encoded><![CDATA[<p>Robert &#8211;</p>
<p>Here is what I&#8217;d do:</p>
<p>1.  Run a repair<br />
2.  Install the December update<br />
3.  Re-run the Hotfix installer.</p>
<p>Nick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Cresswell</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19474</link>
		<author>David Cresswell</author>
		<pubDate>Tue, 22 Apr 2008 08:51:58 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19474</guid>
		<description>Is it just me, but I can't seem to get a connection to many of codegear's sub-domain (except "blogs." of course) these days!?!

Can't even get to www.codegear.com...that can't be good!</description>
		<content:encoded><![CDATA[<p>Is it just me, but I can&#8217;t seem to get a connection to many of codegear&#8217;s sub-domain (except "blogs." of course) these days!?!</p>
<p>Can&#8217;t even get to <a href="http://www.codegear.com...that" rel="nofollow">www.codegear.com&#8230;that</a> can&#8217;t be good!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19472</link>
		<author>Marc</author>
		<pubDate>Tue, 22 Apr 2008 08:03:57 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19472</guid>
		<description>Simply resizing a text box on an ASP.NET Web form can cause Rad Studio 2007 to crash for me. Doesn't look like this will fix it. I also have a bug where if you change the property of a container such as a Panel or UpdatePanel, all the child item events no longer belong to their methods. It means I have to copythe code Rad Studio generates into a comment, the paste it back.What does RAD stand for again?</description>
		<content:encoded><![CDATA[<p>Simply resizing a text box on an ASP.NET Web form can cause Rad Studio 2007 to crash for me. Doesn&#8217;t look like this will fix it. I also have a bug where if you change the property of a container such as a Panel or UpdatePanel, all the child item events no longer belong to their methods. It means I have to copythe code Rad Studio generates into a comment, the paste it back.What does RAD stand for again?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert D.</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19471</link>
		<author>Robert D.</author>
		<pubDate>Tue, 22 Apr 2008 07:07:38 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19471</guid>
		<description>All updates (excluding the new april hotfix) are installed but my BDS Delphi 2007 has version 11.0.2902.10471. Under the section "Installed Updates" there is no entry. And now when i start to install the new april hotfix i get a message "Failed: Could not locate RAD Studio 2007 December Update! Check installation."  Can someone explain me what's going wrong?  Thanks Robert.</description>
		<content:encoded><![CDATA[<p>All updates (excluding the new april hotfix) are installed but my BDS Delphi 2007 has version 11.0.2902.10471. Under the section "Installed Updates" there is no entry. And now when i start to install the new april hotfix i get a message "Failed: Could not locate RAD Studio 2007 December Update! Check installation."  Can someone explain me what&#8217;s going wrong?  Thanks Robert.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C Johnson</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19470</link>
		<author>C Johnson</author>
		<pubDate>Mon, 21 Apr 2008 20:46:19 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19470</guid>
		<description>Luigi -&#62; Oh ya, that's an annoyance for me complaint too - I even have a QC (47032) logged about it.  The unit cache just seems to grow wildly out of control with no consideration for the physical amount of ram available.  When this happens in an VM, the system just crawls to a slow as it has to swap through all those virtual layers just to let you type in the IDE.  Truely, someone needs to revisit that code.

It almost seems that while project groups are great for organization and project management (I use them myself), they are one of the worst things to happen to the IDE performance wise.</description>
		<content:encoded><![CDATA[<p>Luigi -&gt; Oh ya, that&#8217;s an annoyance for me complaint too - I even have a QC (47032) logged about it.  The unit cache just seems to grow wildly out of control with no consideration for the physical amount of ram available.  When this happens in an VM, the system just crawls to a slow as it has to swap through all those virtual layers just to let you type in the IDE.  Truely, someone needs to revisit that code.</p>
<p>It almost seems that while project groups are great for organization and project management (I use them myself), they are one of the worst things to happen to the IDE performance wise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Hodges</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19469</link>
		<author>Nick Hodges</author>
		<pubDate>Mon, 21 Apr 2008 18:23:22 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19469</guid>
		<description>Peter J --

No, this hotfix isn't available via the update mechanism.

Nick</description>
		<content:encoded><![CDATA[<p>Peter J &#8211;</p>
<p>No, this hotfix isn&#8217;t available via the update mechanism.</p>
<p>Nick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter J.</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19467</link>
		<author>Peter J.</author>
		<pubDate>Mon, 21 Apr 2008 14:50:03 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19467</guid>
		<description>Should this update be installable via the Start &#124; Programs &#124; Codegear RAD Studio &#124; Check for Updates menu choice?  If so, mine's not working - it says no update is available.  I had the same problem with the prior Help update.  Why would this functionality be broken on my PC?</description>
		<content:encoded><![CDATA[<p>Should this update be installable via the Start | Programs | Codegear RAD Studio | Check for Updates menu choice?  If so, mine&#8217;s not working - it says no update is available.  I had the same problem with the prior Help update.  Why would this functionality be broken on my PC?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luigi D. Sandon</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19465</link>
		<author>Luigi D. Sandon</author>
		<pubDate>Mon, 21 Apr 2008 08:40:15 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19465</guid>
		<description>I have to restart Delphi when I build/compile a project group containing fifty projects because the IDE does not release memory - a couple of build s and it uses a couple of Gbs. Still not fixed?

And no news about localization fixes? We still cannot deliver localized versions because ITE does not work correctly still.</description>
		<content:encoded><![CDATA[<p>I have to restart Delphi when I build/compile a project group containing fifty projects because the IDE does not release memory - a couple of build s and it uses a couple of Gbs. Still not fixed?</p>
<p>And no news about localization fixes? We still cannot deliver localized versions because ITE does not work correctly still.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C Johnson</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19463</link>
		<author>C Johnson</author>
		<pubDate>Sat, 19 Apr 2008 23:05:19 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19463</guid>
		<description>It definitely seems to help make the problem less obvious, but I still get glitches with that one project.  Maybe it was 2 or 3 bugs at once and some of them are now gone.  On with submitting the bug reports, maybe it can be fixed in the next version. (or at least they can start checking for null pointers more often in the code)</description>
		<content:encoded><![CDATA[<p>It definitely seems to help make the problem less obvious, but I still get glitches with that one project.  Maybe it was 2 or 3 bugs at once and some of them are now gone.  On with submitting the bug reports, maybe it can be fixed in the next version. (or at least they can start checking for null pointers more often in the code)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C Johnson</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19462</link>
		<author>C Johnson</author>
		<pubDate>Sat, 19 Apr 2008 16:50:11 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19462</guid>
		<description>The OpenTools API lets you add entries to the "Installed Products" box in the about box.  Maybe the next hotfix could at least add an entry there to make itself known.

The bug with compiling more than 100 packages, I can generate with a much lesser number, so I am hoping its a similar bug and the fix works for me!

Now I just wish I could figure out why so much as loading and closing one particular project is enough to destroy the IDE.  I am beginning to suspect that it is third party component related, but wow, does the IDE ever go down hard when that project closes.

Btw, the hotfix installs pretty darn quick!  I much prefer that form of patching to installshield MSIs.  I might have to re install it if I do a repair, but since it only took 30 seconds, I don't have a huge problem with that. (And never have with all the previous versions of delphi)</description>
		<content:encoded><![CDATA[<p>The OpenTools API lets you add entries to the "Installed Products" box in the about box.  Maybe the next hotfix could at least add an entry there to make itself known.</p>
<p>The bug with compiling more than 100 packages, I can generate with a much lesser number, so I am hoping its a similar bug and the fix works for me!</p>
<p>Now I just wish I could figure out why so much as loading and closing one particular project is enough to destroy the IDE.  I am beginning to suspect that it is third party component related, but wow, does the IDE ever go down hard when that project closes.</p>
<p>Btw, the hotfix installs pretty darn quick!  I much prefer that form of patching to installshield MSIs.  I might have to re install it if I do a repair, but since it only took 30 seconds, I don&#8217;t have a huge problem with that. (And never have with all the previous versions of delphi)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19461</link>
		<author>Luke</author>
		<pubDate>Sat, 19 Apr 2008 12:45:44 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19461</guid>
		<description>Agreed Fernando! This is the most trivial thing I can imagine! But no, now we'll need paper notebooks to write those things down ("Apr-18: Hotfix no-1 installed").

L.</description>
		<content:encoded><![CDATA[<p>Agreed Fernando! This is the most trivial thing I can imagine! But no, now we&#8217;ll need paper notebooks to write those things down ("Apr-18: Hotfix no-1 installed").</p>
<p>L.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fernando Madruga</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19459</link>
		<author>Fernando Madruga</author>
		<pubDate>Sat, 19 Apr 2008 10:08:09 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19459</guid>
		<description>"Being a hotfix, it will not be part of your MSI library.  Therefore, if you do a repair, you’ll need to apply the hotfix again."

Have you guys or the folks at InstallAware ever read about MSPs? Kind of weird to re-invent the wheel if instead of adding value you remove value from the new wheel...</description>
		<content:encoded><![CDATA[<p>"Being a hotfix, it will not be part of your MSI library.  Therefore, if you do a repair, you’ll need to apply the hotfix again."</p>
<p>Have you guys or the folks at InstallAware ever read about MSPs? Kind of weird to re-invent the wheel if instead of adding value you remove value from the new wheel&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fernando Madruga</title>
		<link>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19458</link>
		<author>Fernando Madruga</author>
		<pubDate>Sat, 19 Apr 2008 10:06:31 +0000</pubDate>
		<guid>http://blogs.codegear.com/nickhodges/2008/04/18/39050#comment-19458</guid>
		<description>"Being a hotfix, it will not alter the About Box at all"

"No harm done", but it would also not be hard for a team of programmers to come up with a nice solution for that! A simple case of adding a reg value with the name of the hotfix when installing it and, in the about box code, reading all values under the "hotfixes" key and displaying them would  not only make it easy to tell using the About box but it would also be easy to know in a programmatic way by reading the proper reg key and values...

This is something that you guys can do in a coffee-break and it would have some added value. Think about a company using 20 or more Delphi's: if they want to be perfectly sure, they have to keep applying the hotfixes over and over! Not the best solution even if "no harm done"...</description>
		<content:encoded><![CDATA[<p>"Being a hotfix, it will not alter the About Box at all"</p>
<p>"No harm done", but it would also not be hard for a team of programmers to come up with a nice solution for that! A simple case of adding a reg value with the name of the hotfix when installing it and, in the about box code, reading all values under the "hotfixes" key and displaying them would  not only make it easy to tell using the About box but it would also be easy to know in a programmatic way by reading the proper reg key and values&#8230;</p>
<p>This is something that you guys can do in a coffee-break and it would have some added value. Think about a company using 20 or more Delphi&#8217;s: if they want to be perfectly sure, they have to keep applying the hotfixes over and over! Not the best solution even if "no harm done"&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
