Brian Evans

Another thing to try - use the older control panel instead of settings. Search for "control" and launch the Control Panel app from the results. Also search for "device manager" and launch that. I remember some manufacturer provided drivers / applications being a problem sometimes so try uninstalling any of those using the control panel and device manager.

If it's hasn't been long since this happened, you can reboot in troubleshooting mode and uninstall the update. As well Dell's suggestions include: - Log in as another user with administrator rights. If you can open the Settings app in that account, create a user account for yourself and delete the old account. - If none of the previous solutions resolved the issue, reinstall your operating system. (Windows 10: The Settings App Does Not Open or Flashes and Closes Instantaneously | Dell US)

Best to run it from a command line with administrator privileges as it installs a service and needs a command line option -i before it will do so. Been playing with it in a Windows Sandbox - Windows Security | Microsoft Learn so I must install it each time since everything poofs when I close the sandbox.

Note the VirusTotal sandbox uses Sysmon - Sysinternals | Microsoft Learn which logs various events based on actions done by anything not just the executable itself like Process Monitor - Sysinternals | Microsoft Learn does.

Not sure there is much of a point in doing that - an AAB provides information so an app store can generate APKs for multiple devices. Using an AAB locally just adds extra steps to building and sending an APK to a device for testing. What's the difference between AABs and APKs? App bundles are only for publishing and cannot be installed on Android devices. The Android package (APK) is Android's installable, executable format for apps. App bundles must be processed by a distributor into APKs so that they can be installed on devices.

Put the extra parameter in ODBCAdvanced for the FDConnection (under Params after selecting the MSSQL driver) or FDPhysMSSQLDriverLink.

Delphi 12 is better behaved on the taskbar than previous versions. No extra entries on the task bar for the running IDE - just one taskbar icon for both. Can now use Windows key + number key to both launch or switch to it. Even works to cycle between multiple running copies of the same Delphi 12. (Win+# are shortcuts for the first 10 application icons on the taskbar).

The dbxora.dll and midas.dll files are available in both the 32-bit and 64-bit redistributable directories. For example for Delphi 12 the redist directories for Windows are: C:\Program Files (x86)\Embarcadero\Studio\23.0\Redist\win32 C:\Program Files (x86)\Embarcadero\Studio\23.0\Redist\win64

Some third-party libraries install a lot of packages - for example, the full Developer Express VCL Components 23.2.1 installs eighty-eight packages in Delphi 12. Something to search or filter the list would be useful when checking if another library and any of its optional packages are installed or not. Would be most used when migrating projects to newer versions of Delphi.

A quick google brings up Dew Research - Math Library Component Delphi Component C++ Builder Component Net A couple hundred channels at 1200hz should be fine on a modern multi core systems with support for some vector extensions like SSE/AVX etc. No real need for a GPU I think.

For older Delphi and newer but for often for different packages I put underscores in front package data/descriptions in Known IDE Packages which I do not want loaded. Delphi packages I have disabled by prefixing their description with an underscore (and why) « The Wiert Corner – irregular stream of stuff

Far as I know MMX only has one set of its own settings that apply to all the IDE's it is integrated with. The position/visibility of any MMX panels in an IDE you would have to set up as you like for the various desktops in the IDE (default, debug etc).

Not sure ARM will avoid the fate of the Motorola 68000 and PowerPC when going against x86 head on. The size of the full x86 ecosystem means there is much more money for processor development so that even when a competitor gets in a few wins it often falls behind over time. ARM has racked up some solid wins due to circumstances that are changing - x86 is no longer stalled by AMD (Bulldozer) or Intel (14nm) with both now making solid progress. Apple added support for the x86 memory access model to the M1/M2/M3 processors which makes running multi-core x86 emulation much easier and higher performing. This means during Apple's transition to ARM the latest x86 based Mac software runs well on the new M1/M2/M3 hardware. Since no other ARM systems currently have anything equivalent it means the latest Windows x86 software will run comparatively poorly on an ARM based system. That makes any transition or even just fielding Windows ARM systems harder as some programs will fare poorly. Apple has really aced the transition to ARM. I think x86 will remain strong due to the large legacy and current software libraries. Same for Windows itself. I do not think Windows for ARM will succeed - it can't run modern x86 software well making any transition off x86 very rough.

I don't use C++ Builder myself, but here is an answer from StackOverflow for a question from a few years ago: you must change two settings. Turn off the Dynamic RTL in the linker settings and disable linking with runtime packages in the package settings. delphi - Can I step into the VCL (Pascal) code while debugging a C++ app? - Stack Overflow debugging - C++ Builder XE2 - is it possible to debug vcl data library? - Stack Overflow

PCRE2 (10.x) was a fork of PCRE (1.x - 8.x) with a revised API so not a case of just updating the library itself. Delphi does need to migrate to the newer PCRE2 10.x from the now no longer in active development PCRE 8.x at some point. In the meantime, there are other regex libraries for Delphi that already support PCRE2.

Without more code hard to tell but keep in mind messages are sent as part of changing the visibility so the event loop can't be blocked if you want the form to go away.

A lot of file types. including PDFs, start with a known byte sequence which also mean they start with a known BASE64 sequence. So, to start with compare the first couple bytes to JVBERi0 . Format Bytes Chars BASE64 PDF 25 50 44 46 2D %PDF- JVBERi0

Short answer: No test case no fix. They do squash bugs when they have good descriptions and can be reproduced reliably. That makes it possible to see, understand, debug, fix and confirm the fix. The release and patch cycles are a bit slow, but it is what it is at this point. I have solved similar freezing issues before, but none were due to Delphi itself. Windows APIs tend to hang when trying to access non-existent network resources. Some old projects referenced common libraries on network shares on servers long gone but still in DNS. Strangest case was dead batteries in a RAID card which caused a Windows cluster to not use write caching - writes were only considered done when they hit the physical disks. Throughput dropped hilariously low for the hardware involved bottlenecking everything. That makes finding a freezing issue in Delphi itself harder without a way to reproduce as what a customer sees might not be due to Delphi itself. Seems like a catch-22 at this point: the freezing robs time from the same people we need to spend time on troubleshooting and trying to find a test case.

Far as I know an object's dependencies should come in through the Uses in its own unit file. You only need to add locally in the test unit anything you are using in your tests. Is the "not" accurate? Makes no sense at all.

Without a way to reproduce it could be a lot of things. Seen code skip a step in a process when a debugger was attached that was added to speed up debug runs looking at latter steps. Also, time the freeze - a consistent over X seconds can be helpful to indicate if it is a timeout like looking up a network name or trying to initiate a network connection to something that doesn't respond at all.

I believe dbExpress is like the BDE - included/available but not really kept up to date at least regarding what is included with Delphi. That is why I suggested the DevArt drivers which have seen more development since the Delphi XE5 days when FireDac was introduced as a replacement to overcome the unidirectional nature of dbExpress. See how dated the SQL Server version are in this list for example: dbExpress Supported Database Management Systems - RAD Studio (embarcadero.com)

Could try a different dbExpress driver for SQL Server like the one from Developer Express (dbExpress Driver for SQL Server (devart.com)). Has a 30-day trial so can test it and then decide. Note the Microsoft SQL Client(s) and versions can be a bit of a mess with 32bit and 64bit being separate and the names changing over the years. Make sure they are up to date and the correct 32 or 64 bit plus older clients are cleaned out.

Looks like "Lock Controls" in the Edit menu is an IDE wide setting that can be toggled on and off. However, it is bugged - the locked state is not applied to the design surfaces of forms created or opened after Lock Controls is toggled on - they have unlocked controls. This leaves us with a toggle that isn't consistently applied so users must toggle it off then back on to get it applied to all open forms. Same for opening a project - even with Lock Controls toggled on all forms are opened unlocked. I created a new ticket for it. There are other related tickets, but none specifically target the failure to apply the current setting when loading/creating forms. [RSP-42429] ON setting of Edit -> Lock Controls ignored by newly opened or created forms - Embarcadero Technologies

For me 11.x series and 11.3 specifically has been a high point but for small reasons - like GetIt no longer being glacially slow bringing up the list of packages and the IDE having more polish / performance in my use of it. Just feels nicer to me subjectively. Some growing pains in the updated IDE and other features but they are, granted too slow for some, improving. There are sometimes offers of discounts on longer maintenance periods and I took the bait last year on a 5-year renewal. As usual a lot depends on how many third-party components need to be renewed / replaced to migrate to a newer Delphi if your current development environment has stayed static for a while.

In C++ Builder you can import/use Delphi units inside a C++ project, so you don't have to convert everything to C++ to get started. C++ Builder is C++ along with bindings for the Delphi VCL and other units so you will be using a lot of Delphi code under the hood even if all your application code is converted to C++.