Leaderboard

I wish the IDE would work! - I wish word searches would not crash the IDE and cause my unsaved work to be lost. - I wish the IDE would not freeze for no apparent reason and cause my work to be lost - I wish Code Insight would finally work - I wish the IDE would not go out of memory after using it for a while To sum up: I want a stable IDE that doesn't waste my time and finally fixes the bugs that have been around for years! am I asking too much?

You might be right but that's not the impression I get from the topics posted.

https://www.quantamagazine.org/computer-scientists-establish-the-best-way-to-traverse-a-graph-20241025/ -tee-

Yes, pretty much - we all know they first ship a half-baked feature to generate marketing hype and then spend the next decade tinkering around the edges to make it work while representatives are telling us "eh, its complicated"

The fact is that any design-time component can crash the IDE. All you have to do is uninstall them all and see if your problem persists. If it does, you can be relatively certain it is the IDE itself and not a component. You seem very resistant to this basic troubleshooting step. That doesn't seem rational. I agree that Delphi quality is not where it needs to be. I do not agree that the IDE is as useless and impossible to use as you have said. Shrug.

In that case I am the unlucky one. Have had no issues using Delphi 12.2 update 1 on Windows 11.

@dummzeuch - I think it is commendable to do your testing on a low powered setup. If it works satisfactory there, it will rock on higher end gear.

my component loads the DLL at runtime and not at design time. I say this because since version 11 I have IDE crashes every day, so I'm led to think that those who comment perhaps don't use Delphi as frequently as I do. However, Delphi 12 when it came out had big problems and I had to wait for the first patch to install some purchased components. In fact, I had opened a ticket on the embarcadero portal and they replied that it was a problem that they were solving. Now I have this problem with the component I created and I opened another ticket and they replied that I am not the only one to have it. It is very strange, in fact it only occurs if I compile in debug, but once I trigger the error (a compiler access violation) I can no longer compile even in release. To be able to use Delphi 12.2 I will have to wait a few more months, that is, when and if they release a patch for this bug too. Can we continue like this? Every time they come out with a new release instead of releasing patches and we are forced to reinstall the entire development environment. In addition, it is advisable to do a clean installation every time because often the version update brings with it many problems. Can we work like this?

TextToShortcut is the problem here, if you can call it that. It compares the shortcut text against some resourcestrings ("Shift+", "Ctrl+", etc.) and if those resourcestrings have been translated then the shortcut strings must also be translated. As far as I can tell (contrary to what I claimed above), if the OP isn't translating anything, then there should be no problem. I would test to make sure, though.

As been said elsewhere, most of us have a stable IDE environment. As long as the Delphi IDE executes code that is written by a third-party, there will be a chance that a third-party component or expert is the cause of instability. And in some cases, the user is the cause. I've written components that were buggy and caused instability until I took the time to find the defect and correct it.

The only way to avoid buffer overflow problems is to write code that doesn't overflow buffers. That won't change with a 64-bit IDE.

Thank you for clarifying. I am pretty sure that goes for 90% of our members here as well.

The (better) solution was at my project: 1) Remove from several locations (especially from the *.cbproj file) this include: (BDSINCLUDE)\windows\vcl don't care how it looks, e.g. also: "c:\program files (x86)\embarcadero\studio\23.0\include\windows\vcl If done the error E2209 Unable to open include file 'vcl.h' should be shown but the error Unable to load Project ... Duplicates not allowed shall be gone. 2) Re-introduce the (BDSINCLUDE)\windows\vcl at one location, i.e.: Options -> Language -> C++ -> Paths and Directories -> System Include Path -> Windows-32bit -> Classic Compiler and compile again, now it worked at my side.

It is a problem for application which make use of a state machine, something I use frequently. Having an event triggered twice add useless complexity at the application level and leads to bugs, especially for "final" event like OnRequestDone. It is better to handle that in the component.

I am using a Fujitsu Esprimo Q920 (released in 2014!) with an i5 mobile processor, 16 GB of RAM and an SSD running Windows 10 for Delphi development (all versions from Delphi 6 -blindingly fast - to Delphi 12 - rather slow but usable). I bought it cheap in a refurbished deal on Amazon.de. It's far from being a rocket, but fine for my hobby software development needs. I also installed Proxmox on a cheap mini PC with an Intel N95 processor, 16 GB of RAM and an SSD I got from Geekbuying (came with Windows 11). I am running a Windows 10 virtual machine on it on which I'm testing GExperts on Delphi 12. That setup is definitely not what I would want to use at work, but again, for hobby software development it is kinda OK. If you leave out the virtual machine part but run Windows directly on the hardware it is faster than the Q920. So: Given enough RAM and an SSD I think basically any current mini PC is OK for that purpose. This may depend on whether you want to use some third party tools and components though. These can slow down the IDE quite a bit. And of course you may think I'm crazy for using such a low powered setup. 😉 Regarding Geekbuying: Beware that that's a platform like Amazon market place. So there are black sheep there. I bought a BMAX mini PC with pre installed Windows 11 from them and it turned out that The pre installed Windows 11 came with some rather dubious software additions, so I tried to do a fresh install. Which turned up that ... the computer does not meet Windows 11 minimum requirements (no TPM, unsupported processor). They must have installed it using the tricks you can find on the web. Which means that it would have had problems with the next major update. But even with these tricks ... the license cannot be used to do a fresh Windows 11 installation. I tried to get a refund but they kept on sending demands for proof (pictures and even a video using some Chinese service) and then simply ignored me. So I definitely don't recommend buying there. (The hardware is rather nice though, if you don't want to install Windows on it.)

I believed it is a different aproach. They give to us something that compiles and is working. Then based on user review and bug reports they are accepting suggestions how to make it work. If everything else fail they buy some source code to make things working again.

- A 64-bit IDE (from community to architect version), as with Lazarus/Visual Studio 2022 - this avoids buffer overflow problems in apps and also database drivers that only exist in 64 bits (it's more difficult find 32-bit drivers for mariadb/mysql); - Automatic code indentation and formatting; - Automatic inclusion of units in the headers, as used; - Community version, lifetime, without registration key or with a key that can be inserted several times, without activating or blocking problems; and also more features such as enabling command line compilation and other possible features for the IDE community to be 64 bits).

@A.M. Hoornweg It is always helpful to indicate what kind of error you get, and where you get it.

I integrated YuOpenSSL into ICS three years ago and alternate using it and OpenSSL for testing. ICS also allows the OpenSSLs to be compiled into applications as resources to ease distribution and DLL hell, all three variants work identically. But applications are larger with YuOpenSSL or resource files. Using SChannel may seem simpler, but your cryptography and updates are then locked to the OS, Microsoft only reluctantly support TLS/1,2 With Windows 2008 but did not support EC certificates, and TLS/1.3 took a long time to arrive. In ICS, I've worked with many of the Windows crypto APIs, and they are horrible. Angus Angus

There are an open issue (an not only one) about that: https://embt.atlassian.net/servicedesk/customer/portal/1/RSS-2144 Seems that the error is about the Visual Assist ... wait for a patch ... (hope for a real patch)....

On iOS, it is common practice to use the identifierForVendor method of the UIDevice class. This value is guaranteed to remain the same for the life of the install (i.e. if the user uninstalls/re-installs your app, it may change). This code shows how to obtain it as a string.

You have the call to ShowDialogAfterTaskFinishes() in the wrong place. TTask runs asynchronously, but you are calling ShowDialogAfterTaskFinishes() immediately after the TTask object is created (and possibly before the TTask even begins to run). You need to move the call to ShowDialogAfterTaskFinishes() inside of the TTask procedure itself, similar to what you have for the call to UpdateMainWindow(), eg: procedure TfQBDailyInvoices.TransferEvent; begin TTask.Run( procedure var x: Integer; begin try for x := 0 to qInvoice.RecordCount - 1 do begin DidWorkorderTransfer := ProcessInvoice; TThread.Synchronize(nil, procedure begin { Update User Interface } UpdateMainWindow; end ); qInvoice.Next; end; finally TThread.Queue(nil, ShowDialogAfterTaskFinishes); end; end ); end; Alternatively, you can use TThread.CreateAnonymousThread() instead, so you can use the TThread.OnTerminate event (which is Synchronize()'d with the main UI thread), eg: procedure TfQBDailyInvoices.TransferEvent; var Thread: TThread; begin Thread := TThread.CreateAnonymousThread( procedure var x: Integer; begin for x := 0 to qInvoice.RecordCount - 1 do begin DidWorkorderTransfer := ProcessInvoice; TThread.Synchronize(nil, procedure begin { Update User Interface } UpdateMainWindow; end ); qInvoice.Next; end; end ); Thread.OnTerminate := TransferEventThreadTerminated; Thread.Start; end; procedure TfQBDailyInvoices.TransferEventThreadTerminated; begin ShowDialogAfterTaskFinishes; end; :