ULIK

Peter, what's your point? If you don't like that feature, deactivate it. I use it often for navigation between extracted code and original position, so I find it very useful.

Just some general thoughts about such an upgrade: - what exactly is the reason for upgrade? Is there a real business case to port? Or is it just because someone wants to use the new fancy things from newer Delphi versions? - as you are asking for a large-scale EHR system: do you and your team have the resources to do it over probably several months or even years? - if the current system is actively developed: can you handle two source branches that may differ heavily over months/years? - as a port to Unicode is involved: what about your existing database? Can it handle Unicode already or is it necessary to upgrade database too. Are existing data ready for Unicode or does it need to be updated too? - check, how good or bad the separation between UI / logic / database already is. Can it be improved on the current D6 system? If so: do it there, where applicable, so that you can see any problems soon and under real conditions. - 3rd party: try to consolidate if there are too much different component collections involved. - new UI features: forget about them at least for the moment. First try to port your application(s) to D12 and then introduce new UI. Only if a new UI components will help you to reduce/replace a lot of existing code or are unavoidable for port, consider adding it. But make sure, that new UI is consistent regarding user input with remaining older UI system. Your end users will be grateful. Depending on who the end users are: are they willing to accept larger changes on UI? Have in mind that training for them may be necessary and who has to pay for it.

Curious, this problem is not restricted on Delphi 12 Athens, You can also see it on (at least) Delphi 11.3 Alexandria. It not necessary to install all that 3rd party libraries. Just DevExpress or ImageEN should be enough to see a relevant delay when opening standard actions. This makes me wonder why none of that vendors have already reported this to Embarcadero.

Uwe, where do I find this groups dialog? Is this a new feature you are working on? Found it! Thanks!

Thanks!

I played around with this expert and added two things: - display with gutter: - two buttons to refresh or clear results: refresh can be used, when typing something on editor itself that modifies the result positions. If you like it, feel free to add it to repository. Please note: all modifications were only tested on Delphi XE11, but they should run on earlier versions too. As I'm not familiar with GX development: I have simply assigned two icons from GX Icon folder to speedbutton glyph, which probably is not the common way for GX. So you might change this to better fit the GX universe. Attached is a patch file with my changes: InstantGrepWithGutter.patch

Minor glitch: label l_PressEsc should set Layout to tlCenter to align it with checkbox (but I'm not sure, if this property is available back to Delphi 7). A suggestion for an interim solution for the missing 'Original Position': procedure PaintFileHeader(_Rect: TRect); ... LineText := Format(SLine, [Res.Idx + 1]); // Add additional text for original position, which is always the very first entry on listbox if _Index = 0 then LineText := LineText + ' (' + Module + ')'; ... You might also use a different color for original position: procedure PaintLines(_Rect: TRect); ... if odSelected in _State then begin BGNormal := clHighLight; LbCanvas.Font.Color := clHighLightText; BGMatch := BGNormal; end else if _Index = 0 then begin // as original position is not a real result, just let it gray BGNormal := clBtnFace; LbCanvas.Font.Color := clWindowText; BGMatch := BGNormal; end else begin BGNormal := clWindow; LbCanvas.Font.Color := clWindowText; BGMatch := RGB(250, 255, 230); end; Just some ideas, but a gutter would be much better. Feel free to add what you like.

I have attached you a Subversion patch file. It's just a quick&dirty change, so have a look on it (especially for the new resource string. This might not be necessary). GX_GrepInstantGrep.pas.patch

I have change the code a little bit and this is my current result of Instant Grep dialog: If the active editor file changes, the dialog changes it's caption too. If you are interested, I can send the necessary modifications.

MMX 15.1.7, Delphi XE 11.3 When opening the drop down menu for visibility icon, icons seems to be missing (as far as I remember earlier versions had shown it) :

Next thing I noticed: I placed the window on a second monitor right beside the maximized IDE main window on first monitor. No problem. Now I closed Instant Grep and opened it again: the Window is placed on my first monitor instead of second one. And how do I clear a former hit list? Entering a blank search phrase does not clear it. Also closing and reopening does not clear it.

Doing a first short test: I was irritated as every hit is divided be the filename. As Instant Grep displays it's result only based on current editor file, why not just add the filename only to caption (see attached image)? Second: I compiled the current source, closed Delphi 11.3 and installed the new DLL. Now the first start showed that error: Following starts do not show it anymore. And why is the roaming profile? Shouldn't this be stored on LOCAL_APP_DATA? Third, if there is no hit I would not show the entry 'Original Position'. At first I wondered, if this was a wrong hit of grep search, because I see something on result list I do not expect. If you want to show the original position, make it more clearer that this is *not* a search result. kind regards, Ulrich

If I remember right: yes, it should work.

I finally found a solution for this problem: the PNG images I printed had no pHYs chunks set (as they were initially created during runtime). As soon as the missing chucks were added, printing from high DPI systems works fine. The point is: it doesn't matter what exact values you are using, it's just that those chunks had to be set to a somewhat reasonable value. function TPaImageStrokeHelper.FixPNGPixelInformation(APNGImage: TPngImage): Boolean; begin Result := False; if not Assigned(APNGImage) then exit; if not APNGImage.HasPixelInformation then begin APNGImage.PixelInformation.PPUnitX := 3780; // relates to 96 DPI: 3780 Points / Meter APNGImage.PixelInformation.PPUnitY := 3780; APNGImage.PixelInformation.UnitType := utMeter; Result := True; end; end;

Oh, didn't realized that you also added an exe. You're right: running your exe I can reproduce this behavior when styles are active.