To eliminate old issues is obviously the best answer to all honest Delphi fans.

Please take a look at this issue. I wondered, why it can be remained in database for so many years.
http://qc.borland.com/wc/qcmain.aspx?d=6417

Fix such kind of issues, thanks

For me it would be much more useful if you solved issues like the very buggy ordering part in Midas.

When I do "order by 1" I want data ordered by the first field, not by the 2nd or in reverse order (I’m talking mainly about D7 here -with Midas.dll from D2006-) but I haven’t seen in Codegear articles any mention that it works right in D2007. That could be a reason to upgrade.

And no, I can’t reproduce it because it seems to work different each time I write a new query, but you could take a look to QC 55581 because it could be related.

By the way, the option to do
Indexfieldnames := ‘FIELD1 ASC; FIELD2 DESC’
is long overdue.

1. Just one word: !
2. Just two words: Merry Christmas! Perhaps I don’t have other occasion and it’s also your day name, isn’t?
3. Just three words: Tiburon field test. Yes, it will be a whole bunch of work to do
and here perhaps that I have a small experience because we dealt with Unicode issues
from several years, now. But perhaps a hidden (for you) problem is (to quote Chris
Bensen) "you use Delphi in a very different way than we do". You see, in our (’our’ here = community) programs the VCL’s presentation layer is almost replaced entirely by 3rd party components, as you (probably) know. So, it will be a rather sequential process in order to test our ‘real world’ projects, because we need to wait those 3rd party vendors. Fortunately (in our discussion) the market it’s pretty mature one so there are few major players in most areas having unfortunately (in our discussion) huge libraries making entire ecosystems (DevExpress, FastReport, IBObjects for ex.). So, my proposal is to start ASAP. Also, another reason is to allow us to test Tiburon without these libs, just with simple programs in which we’ll embed our algorithms/procedures related to strings in order to fix them in a ‘clean room’.

Just my 2c & Merry Christmas again!

The update solved the most annoying problem of the IDE not restoring from
its minimized state when debugging (when hitting the second break point),
but it restored another although cosmetic problem that was eliminated in
previous updates. The "feature" of 2 icons in the taskbar is BACK!… It
looks like a January update may be required to fix this AGAIN too.

Did the restore from minimise when debugging bugfix recreate the second icon on the taskbar? Jeepers I hope you guys fix this too.

Other that that so far so good with December Update.

Doc quality has been one of the biggest core complaints, and we’re still working on it. You should see more improvements in the coming months.

Arturo, sorry we didn’t nail anything you were looking for. Highly recommend you and others interested in these fixes go into QC and add your votes. There are still thousands of issues to go after and we’ll want to go after the top ones first.

Usually that means crashes, broken functionality and regressions. However we do want to improve usability and that’s what it sounds like you are asking for.

Regards,

Chris

Well, I’m sure I’d sigh a big breath of relief. Everytime I need to build my source tree I need to manually remove the read-only attribute to all the files for the IDE can compile. In Delphi 7 I could build all the source tree even if all files were read-only, as they are if you are working with a VCS like Vault. VS2005 doesn’t have this problem either, and I work with a lot of C# projects with the same VCS which IDE integration is, by the way, fantastic (oh yes the grass is so green in VS2005). So yes, if you do use Delphi for more than build shareware MP3 player applications, if you use a VCS and an automated build system, then you know what I’m talking about.

"Arturo, however, I do think you’re descending into whining here. Yes, install-aware is slow, but that’s because it’s MSI based"

Is that so? Then why I don’t have those weird problems and ever-lasting installing processes on VS? All VS installers are MSI based, yet they all work fine. InstallAware is slow because it’s just a bad installer.

I use D7’s help (also installed on my PC) or even refer back to my D5 paper docs.

I don’t know how a noob to Delphi possibly manages to be productive in D2007. This is so in-your-face, it isn’t funny.

But not being able to look up simple documentation because of the "this is foo of class bar" error can halt your ability to develop completely.