dummzeuch

The bug in the Open Tools API still exists in Delphi 11.1 + April 2022 patch. I just re-enabled the code and got an access violation trying to replace a TAdoTable with some fields with a TAdoQuery. You might want to vote for this issue: https://quality.embarcadero.com/browse/RSP-25645

verified and committed in revision #3842 Thanks again.

If I remember correctly there is an API for accessing the Everything data.

Thanks a lot for this. I'll have a look. Could you also please provide an example for a unit which requires this change?

Good point, I had forgotten that I already my data. I have deleted the duplicate now.

The forum software only allows for a certain number of options in a survey, so you will have to use some tricks if you really want to cover all possible Delphi versions.

As always, I'm accepting patches. I currently haven't got the time to implement this myself. Maybe, since to many people seem to want this feature, you could pool some money and even pay somebody to implement it.

I seem to remember that it was fixed in Delphi 11 but I am not quite sure.

I added it around the time I heard about Parnassus Bookmarks, just to see what can be done with standard OTAPI functions. https://blog.dummzeuch.de/2016/01/09/experimental-gexperts-version-1-38-2016-01-09-released/

btw: GExperts has had a Bookmarks Expert for some time. It shows a list of active bookmarks (the standard bookmarks of the IDE) with some context. Not much in comparison to Parnassus Bookmarks, but maybe it helps to lessen the pain for some.

The easiest solution for that would be to disable the plugin if the IDE was not started with /highdpi:unaware and document that restriction. That would help those who miss the plugin but can live without high dpi support in the IDE. Of course there would still be a lot of moaning about this but maybe less than about the total absence of this plugin and any communication about the reason for that. (But that's not going to happen anyway ...)

Sorry, I currently haven't got the time to check. Your best bet is to file a bug report on sourceforge as described in the FAQ which is pinned to this topic. I will eventually get to look there but probably will have forgotten this post by that time.

The following code is supposed to create a TBitmap in 8 bit greyscale: function MakeGrayPalette(_NumColors: TNumColors = 256): HPALETTE; var i: Integer; lp: TMaxLogPalette; Grey: Byte; begin lp.palVersion := $300; lp.palNumEntries := _NumColors; for i := 0 to _NumColors - 1 do begin Grey := i * 255 div _NumColors; lp.palPalEntry[i].peRed := Grey; lp.palPalEntry[i].peGreen := Grey; lp.palPalEntry[i].peBlue := Grey; lp.palPalEntry[i].peFlags := PC_RESERVED; end; Result := CreatePalette(pLogPalette(@lp)^); end; // to be used like this: bmp := TBitmap.Create; bmp.PixelFormat := pf8bit; butBmp.Palette := MakeGrayPalette(); I think I got it from here (stackoverflow) but there are several Google hits for the same code, e.g. here (book "Delphi in a Nutshell") or here (DelphiPower), but I guess the book is the original source. Since it looked fine I never questioned it until I used it today to load a bitmap from a file, modify a part of it and save it again. When I checked the result, I found that in addition to the expected changes there were subtle differences in gray shades varying by a few values. Looking at the code again now, I think there is a bug in the line assigning Grey: Grey := i * 255 div _NumColors; Shouldn't that be ... Grey := i * 256 div _NumColors; ... instead? If I change it like that the bitmaps only contain the expected differences. Or am I missing something here?

Ouch! Yes, of course.

I'm not sure what you're trying to tell me. I had such an example in my test: var X := 0.5; and it seems to work. This was with the "twm" settings because that's what I use. I haven't tried any of the others.

The one in GExperts apparently can do that. I didn't really know but just tested it with: procedure bla; begin for var i: Integer := 0 to List.Count - 1 do begin end; for var i := 0 to List.Count - 1 do begin end; var blub: Integer = 5; Inc(blub); var X := 0.5; var Y := X - 3; end; And this looks fine to me.

You may remember that I was forced to reduce GExperts support for Delphi 6 a while ago, because the IDE no longer started on my computer. It turns out that it was a GExperts bug after all. The fix was simple once I knew what the problem was. And I only found out because carrchri, one of the few GExperts for Delphi 6 users, debugged it and told me. Thanks a lot! When I was able to use the Delphi 6 IDE again I also fixed incompatibilities in the DFMs that prevented some of the dialogs open in Delphi 6. So here is a new release. Apart from these two Delphi 6 related bug fixes there are some improvements ... read on in the blog post.

Committed to revision #3830. I had to fix two event handlers for checkboxes that no longer dis/enabled other checkboxes when (un)checked. Apart from that it seems to work fine. Thanks a lot @TheDelphiCoder!

What is the advantage of doing that?

No, because that might crash other badly written programs.

Is the source code available in an SCM somewhere? That would be the very first step. (No, I'm not a photography enthusiast and I haven't got the time for yet another open source project.)

They are indeed. I'm looking forward to using them one day when my main development environment will have caught up. Currently I'm stuck with Delphi 2007 compatibility at work, just to cater for the two remaining Windows XP computers our programs must run on (Yes, I could upgrade to Delphi XE<LastXpCompatible> but that won't help much.)

Unfortunately not. At least I'm not aware of any and I never wrote one. It's possible that Eric wrote something when he was maintaining the project, but I'm not sure. The part about Delphi 6 compatibility should be obvious, but on the other hand even I tend to forget it once in a while and find out the hard way when the code stops compiling.

I added this message (and the files) exactly because this happens so frequently but still with a time difference long enough that I had forgotten about it every single time. (And I had also already forgotten that I did this. I hope that I will never be the suspect in a crime, because I would have to answer "I don't remember" to most of the questions asked.)

OK, I can reproduce that one with Delphi 10.4 but not with Delphi 2007. This might therefore be some kind of Unicode issue, even though I can't figure out how. btw: It also happens with a much simpler regex: "ix" is enough. If you can fix it, I'll gladly accept a patch of course. If you can't, please create a bug report and include these screenshots.