dummzeuch

I cannot reproduce this in Delphi 2007. Which Delphi version are you using? And what does the GExperts -> Keyboard Shortcuts expert show for Alt+Ctrl+C on your installation? Please answer on https://sourceforge.net/p/gexperts/bugs/114/

If it's not available with full source code, I'm not going to buy it. I have been burned twice with buying components / libraries in binary form only where the company went bust a few years later. Apart from that I like the idea of using SVG for graphics a lot. It would solve several problems I am currently facing.

There are now two experimental options for searching forms that address these issues at least for standard components. The output still needs some polishing.

I think the symbols are a good idea. But why the plus an minus? In the contents tree they signal that you can expand the node (I guess, I haven't installed you tool on this computer). Since the colours are quite easy to distinguish, use the circles without the plus / minus characters.

For the user: yes, for the programmer: no.

For which again you would want to get a complete list, including those units indirectly used.

You can't. Why would you want to? I can only think of a few uses for such a list: Check if a unit is added that should not (e.g. it is being phased out / deprecated) Get a list of 3rd party components to e.g. add to an about box (But that is better done at runtime.) Search all used units for some string (What GExperts Grep now does and the GExperts Open File has been doing for a while) All of these would want to include units that were indirectly added to a project. (I know, I am a bit late to the conversation)

So the idea is simply to get a list of all units linked into the project? That can be done by parsing the map file, if one is being created. And that's a lot easier and faster.

HKLM\Software\WOW6432Node\Embarcadero\BDS\<version>\Library\* and a copy for each user under HKCU\Software\Embarcadero\BDS\<version>\Library\* The latter is the one edited in the Tools -> Options dialog.

Please file a bug report on SourceForge.

The dxGetText installer available from SourceForge has been quite outdated for a while. Via this StackOverflow answer I got this link, where somebody actually went through the trouble to update the tools and create ... https://blog.dummzeuch.de/2018/12/02/using-dxgettext-on-windows-10/

And don't forget the resources spent on fixing that theming stuff, not just in the IDE but also in the IDE extensions. I spent several days just trying to fix things in GExperts that were broken due to introducing the theming bugs in theming bugfixes in theming And I am still not done. And GExperts doesn't even support theming itself, I don't want to consider the time it would take to actually support it (and I am definitely not going to spend that time).

(How do I delete a quote in the mobile interface? Backspace doesn't work.) OK, that's good. As long as the change does not introduce any new problems, I consider the case closed. Thanks for your contribution everybody.

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 https://blog.dummzeuch.de/2019/03/09/gnugettext-pas-using-utf8tounicodestring-instead-of-utf8towidestring/

Utf8Decode existed as an RTL function in older versions (I just checked Delphi 6: It's in system.pas, line 17659). Only in Unicode aware Delphi versions was it marked as deprecated. The gnugettext.Utf8Decode function has already been enclosed in {$ifdef unicode} ... {$endif} since it was introduced in 2012.

I think there is an additional twist: The function gnugettext.Utf8Decode is being inlined, so there is one more possibility for code generation errors. (Took me a while to figure out why my break points in that function never worked.)

It is available since at least Delphi 2009. That's the version I tested with.

I suggested a solution to disable the interbase driver.

Have you tried deleting / renaming DBXInterBaseDriver180.bpl ?

committed. @Sue King could you please test if this has solved your issue?

OK, looking at it again, I still see no reason not to change gnugettext.Utf8Decode from calling System.Utf8ToWideString to System.UTF8ToUnicode. The svn blame function unfortunately does not give any insight because this code was already migrated from Berlios to SourceForge in 2012 and there is no further history available. So I'll commit that change.

On my computer it does not open the file in the IDE but in Notepad++. It simply opens the file with the associated application. And that's the problem: It cannot pass additional parameters for the line number to select, because it does not know which program is called and what to pass for it to jump to the correct line. The only way to do that would be to configure the program to call and which command line it needs. (From within GExperts in the IDE this works, because GExperts knows how to jump to a line number within the IDE.)

Hm, that's odd: if UNICODE is defined: gnugettext.Utf8Decode calls System.Utf8ToWideString which in turn calls System.Utf8Decode (in Delphi 10.3.1) I wonder what caused that Utf8Decode function to be added to gnugettext. Maybe there was a bug in early UNICODE aware Delphis? Or may it's simply because Utf8Decode was marked deprecated at some time. System.UTF8ToUnicodeString contains basically the same code as System.Utf8Decode with the exception that the Temp string is either a _WideStr or a UnicodeString. I'm too tired (I have been banging my had on the table all day to find a solution for a BDE problem under Window 10 😞. It seemed to work at last, when all of a sudden I got a priviliged instruction error 😞 ) to get my head around the implications. For now I see no reason why gnugettext.Utf8Decode should not call System.Utf8TUnicodeString rather than System.Utf8ToWideString, but I'll have to run some tests.

I have asked an admin to remove that post. I have no time now to actually check that race condition you mention.

I think we should not discuss my version in this thread as it is mainly about koskolos' implementation. As I said: I wrote that back when I read about lock free structures but never really tested it thoroughly and lost interest later. It would be too confusing to discuss both in the same thread.