Leaderboard

- IDE is slower than 10.2.3. For example, you can see how Project/Options window is being drawn while opening. - If you set the dark mode, then you can see how options window is first drawn white and then skinned. - Code scrolling in the editor seems bit slower. - When app is run and the closed, lots of windows resizing, flickering is going on while the IDE goes from Debug to Default layout. (The same is happening in 10.2.3 as well, only it does it much faster). - Sometimes after couple of runs Object inspector is not drawn at all until you refresh it. - 1st full recompile of the project took about 12 seconds - 2nd full recompile 40 seconds - 3rd full recompile minute and something - 4th one is still running (joke) - After couple of recompiles, the whole IDE just blurs in the background, compiler gets stuck, and then after some time everything resumes. - Code completion still isn't working in my project (It works after the 1st compile, then stops until project is cleaned). I reported it to QC and even got some response in the item, but then it stopped. When I turned the skinning off, IDE become more responsive, but some of the tool bars are drawn with non default background and when I hover over the tool bar buttons, the background for them becomes black. I'm kinda sad. Usually I install the new Delphi and very soon uninstall the previous one, as the new one is just better. Not this time 😞

Now that Delphi 10.3 Rio is out, we had to ensure that our little mORMot would run with this revision. Since we don't make any commercial software with Delphi any more (we switched to FPC), I downloaded the Community Edition. We disabled the Error Insight feature, which seems not very stable especially with our mORMot complex units - as with previous Delphi versions. In respect to the previous "Starter" editions, this CE version includes everything you expect for good work: Win32 + Win64 + OSX + mobile compilers, and even the source code of the RTL and enabled command-line compilers! The IDE seems really refreshed with its new layout. You feel at home and with some modern and fresh air! Great work Embarcadero! Of course, the "Pro" and "Architect" features are missing (like FireDAC, DataSnap or RADServer). But mORMot is self-contained even for the database access, so with the CE you can write full-features REST/SOA client-servers and MVC web applications, with a simple ORM and high-performance OleDB/ODBC database access to SQlite3, MSSQL, Oracle, Firebird, MySQL and others (by-passing the TDataSet class for better performance) and even NoSQL like MongoDB. Ensure you follow the Embarcadero license terms when you use mORMot with the Community Edition. With Rio, the main breaking change was that the PCRE API switched from an UTF-8 to UTF-16, and did hide the UTF-8 function calls. But after a small patch, now everything works as expected - at least for our regression tests. See http://blog.synopse.info/post/2018/11/24/mORMot-running-on-Delphi-10.3-Rio

Right, so a real project does that because it was put together RAD style where code reuse is king. Wasn't the motto on the Delphi 2 box/sleeve: Encapsulate and Reuse.. Reminds me of my favorite solutions: Reinstall Windows Recreate the dproj file Recreate the Whole Project Rewrite using loose coupling so CodeInsight even comes up ErrorInsight, 'Don't use that'.. Reinstall the IDE How come Andy could fix a good chunk of that without source and for free with IDE Fix Pack?

I have even been at the edge of dropping everything below 10.3 Rio at some point, but the effort to make it compile with the other 10.x versions was not that much (although it just turns out that there still might be some hickups with 10.2.0 to 10.2.2). After all, dropping support for older Delphi versions doesn't take anything away from existing users of these versions. They just won't get any new enhancements. The crucial point for myself is the testing effort for all these versions I don't use on a day by day basis. Given that these tests usually reveal some problems related to that version, that effort often rises significantly.

There was a bug in the (yet unreleased) GExperts code that caused an access violation every time the Delphi IDE was closed. I have just found it, but boy was that difficult! I knew the problem existed in the current source code and by trial and error I found a source code revision that did not yet have it: #2415. So I compared those revisions and step by step narrowed it down to the changes in the unit GX_IdeFormChangeManager in revision #2433 which was a fix for a redrawing bug in the Delphi 10.2 Search Path dialog. So I removed the code I had added ... https://blog.dummzeuch.de/2018/11/24/found-the-cause-of-the-av-on-exiting-the-delphi-ide/

really? Why? Why does that matter? I don't like the intrusive spying of Windows 10 and how Microsoft forces updates on Win10 users. And I never liked Windows 7 (but support for Windows 7 has ended anyway there is only extended support until 01/2020). I don't like Windows 8.1 that much either, but switching to any other version would involve work for no gain.

That indeed has a high impact. My projects are usually free from dependency cycles, but I cannot do much about third party libraries there. Nevertheless can I rarely see problems with Code Insight here. Also compiling is blazing fast and even a full build does not last much longer. In heavy contrast to a customer project I am just working on, where a Ctrl-Click needs seconds to minutes to return and code completion is more of a hindrance than of help. Also I have to re-build the whole project when I make a small change to the interface part of most of the units, because a simple compile won't succeed due to the cycles. I encourage everyone to eliminate those cycles as soon as possible. They cost you a huge amount of your time.

That's exactly what I did (50 minutes ago): https://sourceforge.net/p/gexperts/code/2451/

Perhaps it makes sense to put the code of form detection into a separate unit (if possible)? Then you will not have to add a new dependency between the old units.

Found the cause. It had nothing to do with the Favorites menu. https://blog.dummzeuch.de/2018/11/24/found-the-cause-of-the-av-on-exiting-the-delphi-ide/

As far as Beta bug reporting is concerned there are few things to know. 1. Not all bugs reported during Beta test are resolved during Beta test period. 2. Beta test bugs are tracked separately from main RSP tracker. 3. Beta test bugs that are still not resolved are moved to main RSP tracker project. 4. Moving issues to public tracker requires some administrative work - it is not just simple move all procedure - and it takes some time. At this moment unresolved Rio beta test issues are still not publicly available.

Well, sadly, for me this is expected behavior, and I switch off Error Insight altogether. It is a CPU-time consuming nuisance which (in serious projects) provides only false positives.

I know most of you are already aware of this but I just wanted to indicate that I recently just added *experimental* FMX Support and if everything goes well, I plan to merge it to the official repository. I will appreciate it if you all can help me test support in other supported Firemonkey platforms, I have just been able to test on only the Windows Platform and it seems to work fine. FMX Branch can be found here Instructions on how to Compile the Library for FMX can be found in the FMX Branch README. Thanks.