Well, I honestly, really did think my next post would be about the good in Delphi for Win32 2007, but it turns out that I managed to crash the IDE once more! :( And the worst part of it is that I'm not even trying to do it! I was just trying to setup some Post Build event and experimenting around, because the "much improved documentation" not only describes the build options incorrectly, it also gives no examples of what things one can achieve and how... Now, after consistently crashing every single time I did my builds, it mysteriously stopped crashing when I changed the post build events and doesn't want to crash again even after restoring them to what they were before! Should have made a full folder backup... Now I won't be able to properly submit a bug report... :( [Note to self: start hitting PRT-SCR!]
So far, I can't say that Delphi 2007 has met my expectations... Maybe it's because they were set too high, but if that was the case, it's CodeGear, CodeRage and all those bloggers around that praised Delphi 2007 so much making everyone believe it was rock solid... Like I said above, BDS 2006 had been more rock solid than Delphi 2007 is proving to be...
On the plus side, Delphi 2007 is faster, reloads and re-opens projects faster, and, my #1 favorite feature (as it's the one I've been using most so far!) is the integrated QC client! At least one can now send bug reports in a quicker way...
Just wish I had not used the QC client at all! :(
Subscribe to:
Post Comments (Atom)
6 comments:
We appreciate the feedback. If you have the time, definitely reach out to us so we can understand the issues and make sure we solve them.
I have! So far, I already created 18 reports on QC for Delphi 2007! :)
Ok, I'll have the team check them out. It's very odd since many users are reporting dramatically increased stability - and then you seem to have numerous issues.
Are you available for contact directly if I have some questions on project format and steps for the QC reports?
Chris Pattinson
QA Manager, RAD Studio
Work with the QA team on that - as it looks you are already doing. Adding build events introduces the IDE and build process to outside applications. Outside apps all behave differently, during a build event the IDE launching your external app and is waiting for the app to finish before continuing - if your external app has trouble shutting down it will appear to be hanging the IDE - but the IDE is just waiting for it to finish. My recommendation is to continue working with QA to determine what the issues was. In field test the overwhelming feedback back was that for the last several months testers could not crash the IDE. Adding external apps to build events does add an element of unknown. Thanks for the feedback.
Chris: yes, I'm available. Just check my CDN profile if you need the phone number.
Michael: Yep, I've been posting quite a few entries, although most are non-critical: of those 18, only 2 or 3 were critical and even those were easily overcome. Don't remember if I logged the 3rd one as I was trying to create a simple test case...
I have sooo much problems with ADO components. Well those problems might be for other DB components but I never tried using them. Anyway I add couple of ADO DataSets to project. Save the project and try to reopen it delphi says "Missing connection or connection string".
Okay, now am talking to myself, could be the order of creation made this. I check some components and indeed their Active status has been changed to False as a result of this error. I check ADO connection and it's there working. The odd thing is some DataSets dont produce this error. And when I try to turn those datasets back on Active property says True but delphi pops the same error. Only now I cant compile anything cant even save. Odd thing is, components are working through that dataset since I can see the data in tables. :/ Strange
Post a Comment