Our tests are done and the result is: The new 2 TB drives are as fast as the old ones. So, no worry. The only drawback is that they are smaller. They don’t fit as nicely into the drive enclosures as the old ones. On the other hand, that means they take up less space when stored.

This is nothing to write home about, really, just a small change:

Previously when starting the tool, the main window was shown for a short time before it got hidden. Now that no longer happens.

Don’t now what this is about? You are probably lucky then and don’t need this tool. But if you still want to know, go to the dzEditorLinenedsFix page.

In December 2017 I wrote about the new model of 2 TB Seagate Barracuda drives becoming unusable for us because writing performance dropped significantly after a few seconds of continuous writing to them. We do a lot of this because there are several cameras on our measurement vehicles that write one picture every metre while we are doing road condition surveys at 80 km/h (that results in about 20 pictures per second). These new drives just were not up to that demand. Our guess was that it was caused by Seagate reducing the number of platters in the drives and adding some RAM cache to make up for it. This works mostly fine for normal office work where you rarely copy large amounts of data.

That problem disappeared because for whatever reason the old model reappeared on the market again. So for 2018 we could just buy that old model and everything just worked.

Unfortunately with the arrival of 2019 we are back to square one: The old model is only available in small amounts of remaining stock. We will test the new model again and see whether it has been improved, but somehow I doubt it.

EDIT: Our tests are done and the result is: The new 2 TB drives are as fast as the old ones. So, no worry. The only drawback is that they are smaller. They don’t fit as nicely into the drive enclosures as the old ones. On the other hand, that means they take up less space when stored.

A few weeks ago, Sue King contacted me because there was a problem with using dxGetText together with the Nexus DB components.

For Unicode aware Delphi versions gnugettext.pas declares a function utf8decode which calls System.UTF8ToWideString. After replacing a call to utf8decode with UTF8ToUnicodeString the problem went away.

Since I don’t want to break backwards compatibility with non Unicode Delphi versions I have now changed gnugettext.utf8decode to call UTF8ToUnicodeString instead of UTF8ToWideString.

I can’t see any problem with this change but I am far from being an expert on Unicode related issues. So, if you find any problem with this change, please comment on the corresponding topic in the international Delphi Praxis forum.

The GExperts Grep Search expert has various options to tell it which files to search:

• The current file
• All files in project
• All files in project group
• A directory list (separated by semicolon)

That sounds like an exhaustive list, but it isn’t. Both, project and project group, were only searching files explicitly listed in the project(s). Files that were linked into the project using the search path, were not searched.

Until now, that is: There is now an option to use the MAP file instead of the DPR file for project search.

The MAP file is created by the linker and contains a list of all source files linked into the program. By default, that file is not created though, you must explicitly enable it on the Linker page of the project options.

The least detailed setting “Segments” is sufficient for the new Grep functionality. If there is no MAP file, it falls back to the original method of searching files listed in the DPR file.

Beware that this will also search units located in the RTL / VCL and FMX source directories. This might not be what you want. I plan to add some more flexibility in the future.

There is no release yet and it might take a while until I feel like doing one, but you can always compile your own GExperts DLL. Make sure you delete the existing directory AppData\roaming\GExperts\DelphiXXX\UsesExpertCache when you replace the DLL with the new one.

Discussion about this post at https://en.delphipraxis.net/topic/793-gexperts-grep-can-use-the-map-file/

I just read about a possible problem with the JvHidControllerClass under Windows 10 1809. I haven’t tested it but I post a link to a workaround here just in case I ever need it and might not find it again:
https://www.delphipraxis.net/1426728-post4.html

If you get the error “PrivateGXMenuActionManager is not nil upon creation” when starting your IDE, check the entries under

HKCU\Software\Embarcadero\BDS\<version>\Expert

There are most likely two entries for GExperts. Remove one and the error should go away.

These entries come from

1. The installer (GExperts=”path\to\dll”), because it always uses GExperts as the name for the entry.
2. The Expert Manager (GExpertsXxx=”path\to\dll”), because it uses the name of the dll file for the entry.

Yes, this is a bug. And it has been fixed on 2019-03-02.

Discussion about this post here: https://en.delphipraxis.net/topic/785-gexperts-error-privategxmenuactionmanager-is-not-nil-upon-creation/

Delta Chat, a chat program that uses e-mail as the transport protocol and supports end to end encryption, is now available in the beta channel of Google Play.

If you are already using an older version, you will have to backup your data, uninstall it, install the new version and import the data.

This worked flawlessly for me

I’m using it with an separate e-mail account which I have created for it, so it does not clutter my existing e-mail, but in theory it should be able to coexist.

Nice summary by NGLN on StackOverflow of the way a ShortCut travels through the Delphi VCL

https://stackoverflow.com/a/27083262/49925

I recently had a problem with access violations when calling methods of interfaces. The reason turned out to be duplicate GUIDs in the interface declarations. This caused AVs because the wrong methods were called and the parameters passed to them were not of the right type and numbers. Duplicate GUIDs are usually caused by copying existing interfaces and changing them, without also generating a GUID for the copy. (Btw: The Hotkey for generating a new GUID in the Delphi IDE is Ctrl+Shift+G.)

So I looked for a way to find all interfaces and their GUIDs in my program. There is a uInterfaces.Duplicates unit on GitHub which claims to retrieve this list. Unfortunately I needed this for a Delphi 2007 program and Delphi 2007 does not come with a System.RTTI unit, so this was not an option (and therefore I don’t know whether this unit would have worked).

StackOverflow didn’t help much either, apart from David Heffernan’s suggestion to parse the source code.

So this is what I did. I used GExperts Grep to search for GUIDs, or more eaxct: For the pattern that is used to add a GUID to an interface declaration in Delphi.

It always looks like this:

type
ISomeInterface = interface ['{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}'];


Where X is a hexadecimal digit in upper case.

The Regular Expression for this is:

$'\{[0-9A-F]{8}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{4}-[0-9A-F]{12}\}'$

The literals [ ] and { } must be escaped with a backslash because they have special meaning in a RegEx. [0-9A-F] means one of ‘0’..’9′ or ‘A’..’F’ which is an upper case hexadecimal digit. {4} means four of those {8} means eight and of course {12} means twelve.

You have to turn off the option “Whole Word” and turn on “Regular Expression”. Of course this needs to search at least all files in the project.

Why do I say “at least”? Because actually it needs to search all files linked into the project, including any packages if such are used. “All files in project” only searches files listed in the DPR file, so it’s potentially missing quite a lot.

Which, again, reminds me that I wanted to extend Grep Search to search all files in the MAP file. Code for getting that list is already in place and being used e.g. in the Open File Expert. I “just” need to put the pieces together.

I’m thinking about making yet another Expert out of this, that not only lists all GUIDs but shows a list of Interface names and their associated GUIDs and of course checks for duplicates.