Leaderboard

After getting tired of clicking the wrong one, I created some simple taskbar icons for Delphi with an apparent version shown. Currently there are icons for Delphi 10 Seattle Delphi 10.1 Berlin Delphi 10.2 Tokyo Delphi 10.3 Rio Delphi 10.4 Sydney Delphi 11 Alexandria This is an example for Delphi 11: And this is what my taskbar now looks like: All these icons are available on GitHub: https://github.com/UweRaabe/DelphiIcons

Doing their best to avoid an even bigger disaster?

Finally: Announcing the Availability of RAD Studio 11.1 Alexandria

We have no idea as it's most probably sealed by NDA agreement.

And now comes the long-standing debate we have with ourselves: "Do I take the risk and download it? Or do I wait until some other poor schmoe becomes an unwitting tester" I'm soooo tempted to give it a try!

Hi ! I've just published the source code in Pascal/Delphi of "Vidi Language" v0.2-alpha: https://github.com/davidberneda/Vidi It includes a parser/compiler and a simple ide/debugger for a new programming language (Vidi). This is a toy-experiment project in a very early stage. Attached pdf reference, same here: https://github.com/davidberneda/Vidi/blob/master/documentation/Vidi_Language_Reference.md regards david Vidi_Language_Reference.pdf

The complete VCL package includes more than 760 VCL components including popular packages like LMD DockingPack, GridPack or LMD DialogPack (available for Delphi/C++Builder XE2 and better). Major changes in this release are the redesigned RichPack and common PrintPack package. New controls were added to LMD-Tools (new Font/Replica image list controls) along with dozens of requested improvements and fixes. Color schemes and JSON support were added to LMD SyntaxEdit; DemoCenter and AnyLogger app were updated (e.g. using the new scalable font icons). Please check also Tutorials Page to review several new and updated documentations. A list of all changes can be found on LMD VCL What’s new page. Check the new trials and compiled Exe-Demos at https://www.lmd.de/downloads Feature Matrix of all LMD VCL products: https://www.lmd.de/feature-matrix If you are interested in purchasing check out the order Page: https://www.lmd.de/shopping  If any questions are left, please contact us at mail@lmdsupport.com!

I just observed that my Android app suffered a MASSIVE decrease of compatible devices after a new release with 10.4.2, compared to 10.3.3. Please see attached screenshots from Google Play's "Release Dashboard": App bundle 2.9.3.1 (compiled with Delphi 10.3.3. CE) was still compatible with 18.885 devices. 10 month later, I released an update with Delphi 10.4.2 CE which was only compatible with 6702 devices! Do you experience the same with your apps? Or what do you do to maintain device compatibility? Does SDK version has something to do with it? Please note also file size. In order to satisfy users, that could not install the newer versions, I compiled a 32 bit .apk and placed it on my website. It does the job but that cannot be the solution.

What do you think all the beta testers did during the last weeks?

Fill in the unit name before the function name!

https://docwiki.embarcadero.com/Libraries/Alexandria/en/System.StrUtils.SearchBuf Suggests it is now in the AnsiStrings unit.

I also got the impression that quantity of content is preferred over quality of content. This may be based on the way social media works these days. I mean, how would they be able to even detect quality with their algorithms? Beware the day when MVP turns into an abbreviation for Marketing Voluntary Populist

They don't have to answer each and every question here and elsewhere. They just need to issue a statement. Once. After having endured the amateurish execution of the last few webinars I for one will pass on this one. They badly need a professional, grownup to handle these events. After DelphiCon 2021 my client asked me if I could suggest which replays they should watch. I've pretended to forget about that because I'm frankly embarrassed about it.

In this case, I use a bog standard %s in the string and Format before passing to FireDAC. I like the macro idea and did have a look but might be worth trying it out.

A table name cannot be treated as a parameter. Instead you can use a macro like this: DELETE FROM &TableName and then set the actual table name with MacroByName.AsIdentifier := DestinationTableName;

I'm sorry but that is a joke not a roadmap. A couple of years earlier they have had real roadmaps. With information like when will be the next release and what we can expect (sometimes even a couple of minor versions). Now just Now / Next with no information. I'm sorry but that is not enough to plan release cycles and upgrade path for a production environment where you've to plan time for the upgrades in the code base. It's not always enough to install the new IDE, recompile and ship to the customers.

If only there were someone at Embarcadero specifically tasked with communicating with the customers...🤔 Maybe @Jim McKeeth knows someone who can tell us what the hell is going on?

Someone at EMB or IDERA should communicatie then why problems are not solved as expected. But communication besides sales spam is the biggest problem for EMB. (this is again a plus point for moving to another dev platform, the minus points are not holding it for many years i think)

AFAIK, they have outsourced at least some parts of their development to a huge center in Ukraine - maybe that's an explanation.

Thank you, Dave! Changing %minSdkVersion% value in AndroidManifest.template.xml in combination with adapting NDK settings as per your (quoted) article increased the number of supported devices greatly! I tried platform android-19 fist, but that threw an error, so I settled with android-21. It should be stressed that changing only %minSdkVersion%, as suggested by Philipp, does not do the job, as this "fakes" an environment which strictly doesn't exist. My substantial main error though was, that I deleted target platform Android 32 bit from project manager in app version 2.10, caused by my misunderstanding of Google's policy, that apps have to support 64 bit from last August on. That does NOT mean, that app bundles should not also include a 32 bit package! Older devices obviously only accept 32 bit apps. Now, with re-installed Android 32 platform and android-21 NDK platform settings, I am back to 17.463 devices. 🙂

Change the %minSdkVersion% value in AndroidManifest.template.xml to something lower than 23 but not lower than 19 (Android 4.4). You'll also need to ensure that the NDK settings are also changed, as per the "Important information about the NDK settings" section in this article: https://delphiworlds.com/2020/09/manual-android-sdk-ndk-install-delphi/. Note that if you target API level 19, projects containing any datasnap components (eg TClientDataset) will not compile.

You find two entries in AndroidManifest.xml (here with Delphi 11): <uses-sdk android:minSdkVersion="23" android:targetSdkVersion="30" /> So you have to compare not only the targetSdkVersion but also the minSdkVersion. Perhaps this reduce the number. You can set minSdkVersion manually in the Delphi 10.4.2 to the same value as in the Delphi 10.3.3 version to compare the number of devices then. But you can´t be sure that the Delphi 10.4.2 APK-file is running on Android devices with a lower sdk as with the default Delphi 10.4.2 value.

Making it available to everyone who want a thread safe, asynchronous, cross-platform and simplistic messaging system for communication between classes / layers in delphi applications. https://github.com/viniciusfbb/ipub-messaging

I recently upgraded my old C++ Builder 2009 to C++ Builder 11. It was time .. and I wanted to make use of the new GUI improvements (Styles, Scaling, High DPI etc). GUI stuff in other words. To that end I spent a lot of money to get a license. Everything is relative, but to me this is the biggest investment in quite some time and the biggest software investment ever. I have always been happy with Builder 2009 and yes, there were some issues that I had to work around, but not too many. Since I have upgraded I have already reported close to 20 bugs. Never ever did I have to .. It's also making me nervous as to when these things will get fixed, if at all, as it impacts my work. The silver lining at least was that my bugs triggered interaction. I saw them being escalated to development or they were assigned to me again to provide more information. All that has stopped in the last few weeks. For all the last bugs there has been zero interaction. Nothing, as if nobody cares. The GUI work involves custom controls for which I need the help files, to be able to apply the Styles properly etc. In itself already poorly documented but for 3 weeks now docwiki has predominantly been unavailable. There are already other posts about that, so I won't get into the specifics of that, but it adds to what looks like a systemic failure. - Many bugs in the very features they're touting about and that convinced me to upgrade - Nothing appears to be done about it, nobody seems to care - Docwiki offline, nothing seems to be done about it, nobody (at embarcadero) seems to care The person most responsive in QA before and who has not responded anymore has a Ukrainian name. Perhaps coincidence, perhaps my paranoia but how exposed is Embarcadero development and support to Ukraine. Is this the reason for all the recent issues ? If so, communicating about it would at least renew confidence. All this nonsense would not be necessary if they would just COMMUNICATE about the issues (docwiki for instance). The silence only feeds the idea of a failing company or at least a failing product and I feel bad for having invested my time and money in this at this stage. My 'happy life' with Builder 2009, the type of work I'm doing with it and the low exposure to issues may have made me blind to something that is well known and has been happening for years ? I don't know ? Maybe I shouldn't worry because this is business as usual ? In which case I wish I had done my homework though.

In the quality portal you get response while they validate your report and try to prove it's how the product works and not a bug. After that unfortunately there is no response at all (not even in which version and time frame when the fix will be shipped). Usually you will get no response about the issue at all. Do I think this is the right way? Of course not. As sometimes it's critical to us to know how to communicate with our clients as we have also to plan and communicate to clients when we can ship the fixed product. For some unknown reason who ever decides the future of the product cuts off the communications with the developers (there was a brief period when even on this forum you was able to get honest answers). Instead of a clear communication we can get only promotion materials how everything is nice and shiny (and that's true when you try hello world applications, but as soon as you try to do something more complication you will discover bugs). For me the latest bad sign is that they abandoned the idea that we should have a roadmap. Now you can only read the future of the products only from your coffee mug and that's not a fun thing to do when my managers asks me what is the next step.