Uwe Raabe

Can you revert the update to see if it can actually be the real cause?

What types are dsetAddUser and tbAddUser and how are they related?

Where do you specify the table name the insertion is supposed to go?

9 minutes ago, zed said:

b := StrToDateTime('00:00') + 1; // 24:00

Well, that can obviously be simplified to b := 1;

16 minutes ago, Marsil said:

(the funny thing here is that I had to uninstall the whole thing not just help, no option for help uninstall only )

There is! Via the IDE menu select Tools - Manage Platforms, then switch to Additional Options, uncheck Help and click on Apply.

You can achieve the desired result with TTimeSpan:

  diff := TTimeSpan.Subtract(ET, ST).TotalHours;

40 minutes ago, gkobler said:

Same to mee, but at the moment no solution! May it's a Delphi problem.

That may indeed be a problem with Delphi and/or the TreeView control. MMX suffers from the same symptom.

As said, the error is not the search itself, but the refactoring part of the search menu, which barfs on some source code. As the underlying parser will be replaced by an LSP based one in the future.

If you have no need for the refactoring at all, you can just disable the package in the Delphi registry: Known IDE Packages, $(BDS)\bin\refactoride280.bpl, edit the value and insert two underscores at the beginning.

No guarantee, that the IDE will not get somewhat unstable by this. In that case revert the change.

AFAIK (and I'm pretty sure of that), the full path is just for display and was never supposed to be edited. If you want to change it you need to remove that package and add the other one.

5 minutes ago, KenR said:

I cannot edit the path of the selected package at all.

And you are really sure that you were able to do so before you installed GExperts?

3 hours ago, balabuev said:

IDE restart helps.

Next time please try if just closing and reopening the project is sufficient.

16 minutes ago, Sherlock said:

All I ever see is drawbacks to this kind of software development.

There are types of applications that benefit a lot from this concept, where I can hardly imagine how it would be without it. Just to name a few I heavily work with: Delphi IDE, RAD Server and FinalBuilder.

Delphi 11 supports Monterey, but Delphi 10.4 does not. So upgrading will be a solution.

https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Supported_Target_Platforms

https://docwiki.embarcadero.com/RADStudio/Sydney/en/Supported_Target_Platforms

Enterprise

4 minutes ago, André Souza said:

Could it be that the fact that you had an old version and installed it and then installed a newer one, left something new that doesn't give the bug.

No, the Delphi version I tested the fresh KSVC installation had never had installed them before.

Probably the TDBEdit has its AutoSize set.

I still cannot reproduce with Build 0937 and the latest KSVC from GetIt.

22 minutes ago, André Souza said:

You reused the old package

Yes, the package is the same as it has been with previously installed Delphi version.

I will try again with a fresh KSVC installation from GetIt.

If I understand it correctly this is a FastReport issue caused by a new version. So if you opt to update FastReport you have to compile your appication with the new dcp files and deploy it together with the new bpl files.

Nevertheless, you should be able to keep it compatible by using the old FastReport dcp files when compiling the project.

Same here, no error.

On 8/13/2022 at 3:56 PM, Tom F said:

Is there a way to show the "old style" (with a tree) when using styles??

Actually, the tree style dialog is the new one. The drawback of the new ones is that they cannot be styled, because they are completely handled by Windows.

TSaveDialog tries to use the newer dialog when possible. With styles active it is just not possible and the old style dialogs are used.

Besides the hint from Renate you can force the (unstyled) new dialog when you replace the TSaveDialog with a TFileSaveDialog.

In this case the feature is the ability to write identifiers in Unicode, but I would rather call that an abomination than a feature.

The (TPNGObject) reference in the Object Inspector implies that the DFM contains an old TPNGObject instance. This can happen when that DFM was created in a Delphi version before D2009 or with the old PngObjects library. Since Delphi 2009 the corresponding graphic class is named TPngImage.

The PngComponents packages are by default compiled with RegisterOldPngFormat defined. Unless you define the same in your application it cannot recognize the TPNGObject instance in the DFM.

To convert from TPNGObject to TPngImage simply open the image in the IDE designer as you already did. Then save the image to disk and load it again. After that the Object Inspector should have (TPngImage) and your application will work without the define mentioned above.

If anyone experiences this, it would be helpful to capture the current state of the unit. Then we can inspect these units to detect similarities.

I remember a case when Code Insight breaks after static string array declaration. It can be that we have something similar causing the behavior seen sometimes.

Sorry, I cannot confirm this.

JM2C, if your application runs fine as 32-Bit I would leave it as is. At least the development in the Delphi IDE will give you a better experience. It doesn't hinder you to provide a 64-Bit version on top.