Possible issue with Eureka Log and Delphi 2010

[jacobhoover]

EL: 6.0.23

I'm experiencing a somewhat random issue while using Eureka Log within Delphi 2010. Delphi 2010 introduced the concept of option sets. By default, every project comes with a debug and release set, which is derived from the base. I have gone through and fixed all projects so that EUREKALOG and EUREKALOG_VER6 are defined in the base, and that DEBUG is only defined in the DEBUG option, and RELEASE is only defined in the release option.

The bug I am experiencing is that DEBUG keeps getting rewritten as a base option, which causes DEBUG being defined for the RELEASE configuration. I have yet to disable the expert in the IDE to see if it has any effect, but one would assume that the IDE feature would have been functionally tested before being released. EurekaLog is the only 3rd party tool we have installed other than the default designer packages provided with the IDE.

I've browsed the source for the expert, but I can't seem to find what allows Eureka Log the ability to rewrite the DPROJ/DPK files.

Has anyone else reported a similar problem? Is this a known bug with the IDE?

[Alex]

Hi,

Sorry for the delay.

I was trying to reproduce this behaviour, but failed to do it.

I've created empty project, entered EurekaLog-related defines in base profile and enabled EurekaLog. I've saved, compiled, switching between profiles, wrote some code - no matter what I did: the base profile didn't change. It has only EurekaLog-related defines. DEBUG and RELEASE defines are in their place, not in the base profile.

Can you specify the exact steps to reproduce the problem? Try also to install the latest version of EurekaLog (the beta RC version) and Delphi (the latest service pack/update) - if it is a bug in EurekaLog or Delphi, then it can be already fixed.

[jacobhoover]

I'll try and see if I can reproduce this issue on a clean set of projects.

It may be worth mentioning that we are using multiple BPL projects along with the exe. All of these projects were originally created in Delphi 4 or 7, and were upgraded to 2006 (where they all worked fine) and then to 2010.

The compiler defines are one of a rather large set of symptoms we are experiencing. The most annoying one is when object inheritance of DFM files gets broken, causing all descendant DFM files to be corrupted. At which point, we have to revert to the last version in our SCM to recover.

I was hoping there was an obvious bug in Delphi that someone has all ready found, as trying to search the EDN for bugs is as about enjoyable as getting a root canal.

For reference, we are using EL 6.0.23 and Delphi 2010 with Update 5 (Database Pack) and Help Update 2.

[Alex]

Hi,

Are you using other 3rd party experts?