Re: Delphi 2005 Update 4 IS needed !!!
- From: Jeff Wormsley <jwormsley@xxxxxxxxxxx>
- Date: Mon, 25 Jul 2005 13:55:23 -0400
Dan Miser wrote:
I love how D2005 Enterprise works, too. People will read the negative and give it far more weight than reading the positive and believing it. I don't really care. I'll just keep pluuging away happily while others stand on the sidelines.
I like how it works as well, when it works. DCM'ed Win32 is ok, rarely any problems. Full version to do VCL.NET crashes on me very frequently, though.
1. Loading - Sometimes it doesn't even load, just hangs and I have to kill it with task manager. It seems, but isn't certain, that bringing another app to the foreground while the splash screen is up either triggers it or makes it happen more often. If I sit there for the whole 1+ minute load, it doesn't seem to happen.
2. Whatever you call the bit where leaving the mouse over a word shows the unit/assembly the word is declared in, plus the calling convention if it is a function or procedure will occasionally hang the whole system. This seems to happen if you pull the mouse away after the box is drawn but before the text is filled in, and where your mouse moves is another identifier. Again, while it happens a lot, it isn't 100% reproducable.
3. App crashes running in IDE give 0 output as to why in some cases. It seems that it happens when calling an unmanaged DLL entry with incorrectly marshalled parameters. The app hits the offending call and simply terminates. No debugger window, no exception, no nothing, just bam, back to the IDE. Doesn't matter if you just run, or single step. This isn't the disappearing IDE problem. I've never seen that one.
4. Failure to shutdown. Occasionally, when you shut it down, it hangs and has to be killed with task manager. This is rarer than the others, and I don't particularly mind it.
These issues make using VCL.NET a pain. I don't use this for my own apps, but I need to develop an assembly for someone else, and so I have my test code as VCL.NET for now. The assembly won't have any GUI, but it is easier to test the code that will go into it this way. If I had to do more than a trivial wrapper app this way, I'd scream. However, since doing some work in eVC++ a few months ago, I'm used to buggy IDE's that crash. :) Fortunately, the Win32 only config from DCM has none of these problems, and I have released one larger app with it, and am not worried about others should I feel I need to migrate them from D6.
Jeff.
P.S. System is WinXPSP2, D2005 update 3 applied .
- Follow-Ups:
- Re: Delphi 2005 Update 4 IS needed !!!
- From: Dan Miser
- Re: Delphi 2005 Update 4 IS needed !!!
- References:
- Delphi 2005 Update 4 IS needed !!!
- From: Dave Hamdon
- Re: Delphi 2005 Update 4 IS needed !!!
- From: Pete Goodwin
- Re: Delphi 2005 Update 4 IS needed !!!
- From: Loren Pechtel
- Re: Delphi 2005 Update 4 IS needed !!!
- From: Bob Dawson
- Re: Delphi 2005 Update 4 IS needed !!!
- From: Loren Pechtel
- Re: Delphi 2005 Update 4 IS needed !!!
- From: Bruce McGee
- Re: Delphi 2005 Update 4 IS needed !!!
- From: John Jacobson aka Captain Jake
- Re: Delphi 2005 Update 4 IS needed !!!
- From: Dan Miser
- Delphi 2005 Update 4 IS needed !!!
- Prev by Date: Re: Roadmap issue
- Next by Date: Re: More fuel for the 64-bit fire ...
- Previous by thread: Re: Delphi 2005 Update 4 IS needed !!!
- Next by thread: Re: Delphi 2005 Update 4 IS needed !!!
- Index(es):
Relevant Pages
|