FredS

Not really, that searchable data had huge value. Most weird issues/errors had many iterations of fixes and additional information. Certainly while stuck with several of those over the years a quick search was all that was needed.. its the difference between a few minutes and an extended pause..

Assuming you have no 'explicit COLLATE ' in your tables you can use ALTER CHARACTER SET on an empty DB and batch move data into that. Or add this to your creation statement, keep in mind there where speed issues with UNICODE_CI_AI until v3.07: CREATE DATABASE :FileName USER :UserName PASSWORD :Pwd PAGE_SIZE 16384 default character set UTF8 collation UNICODE_CI_AI ;

You mean while they repeatedly shut down and wipe historic info from the newsgroups and the forum for extended periods? Because I thought it was a perfect split, SO for code stuff and those Newsgroups and Forums for hard to figure out errors and missing documentation.

This has been an issue on and off for a while now. Projects don't even need to be very large for it to happen and its better in one release then comes back with an update. Steps that helped, depending on Release version: Remove all source but your project's from accessible paths, GetIt does the opposite.. This means pre-compile Components in both Release and Debug Use a Clean.bat which removes all DCUs that may have been compiled using different directives. For me this was key, switching configuration outputs DCUs to a different subdir but for some reason Delphi failed to comprehend that. Eliminate all circular references, MMX works well for that.. Not something that would happen if Delphi was still built with Delphi.

Try deleting your entire DCU Output directory before compiling. Note from a clean.cmd I execute via Build Tools: After using Gexperts clean a lot of compile issues went away, I have always guessed that this IDE bug that breaks 'Build Groups' and all compiling with linking errors is a folder salad created by the IDE.

Only because the CE version isn't out yet, those guys still have hope in issues being solved in real time 🙂

Aren't you freeing the form twice? caFree calls Release, Release posts a CM_Release message and that calls Free..

Installing MMX15 slowed down everything, had to manually change prior Delphi versions back to 14.. plus those new images aren't my taste to be polite 🙂

Why should you care? Aren't you a paying customer? When a bug stops one of your customers does he care how complex that is for you to find? Let's be clear here; I've watched plenty of good developers both find the bugs and supply workarounds which where never implemented.. How nice would that be if your clients had to both find it, explain it in detail and fix it for you?

But guaranteed no more than the compiler can understand.. the rest are excuses..

That is what the LSP was supposed to solve since Godzilla, No?

Do you see the HelpInsight window come up, Including the Summary text? This is the original method with the Remarks section removed using Ctrl+Shift+H:

Not the case here, when I first moved the cursor over I got a 'calculating..' followed by 'canceled' or maybe 'removed' then moving the cursor slightly again gives a frozen 'calculating' followed within 2 minutes by a Stack Overflow and a hard crash.

First, empty shouldn't be unusual. Second it was a bulleted list not empty.. Filed: RSP-33091

I will, however one has to question how that passed through QA 🙂

I disabled all Experts, and this is reproducible on both Windows 7 and 10.. FYI: The original error is from a larger project and had a bulleted list in the remarks section.. As for clean install; the Win10 is clean the Win7 an upgrade, both 10.4.2 Pro.

There are no international characters that should be (ANSI): /// <summary> /// Shift+Ctrl+Alt allows access to Custom.Ini /// </summary> /// <remarks> /// </remarks>

Apparently I have a new marketable skill, crashing the LSP server.. This is unbelievable, can someone verify that these steps are reproducible? New VCL Project Add an event handler for 'KeyDown' Paste this DocInsight text Save Hover your cursor over the implementation of 'KeyDown' exception class : EOleException exception message : Stack overflow. thread $f4c: 514f25e9 +89 xmlrtl270.bpl Xml.XMLDoc 2071 +1 TXMLNode.GetIsTextElement >> stack will be calculated soon unit Unit1; interface uses Winapi.Windows, Winapi.Messages, System.SysUtils, System.Variants, System.Classes, Vcl.Graphics, Vcl.Controls, Vcl.Forms, Vcl.Dialogs; type TForm1 = class(TForm) /// <summary> /// Shift+Ctrl+Alt allows access to Custom.Ini /// </summary> /// <remarks> /// </remarks> procedure FormKeyDown(Sender: TObject; var Key: Word; Shift: TShiftState); private { Private declarations } public { Public declarations } end; var Form1: TForm1; implementation {$R *.dfm} procedure TForm1.FormKeyDown(Sender: TObject; var Key: Word; Shift: TShiftState); begin ShowMessage('LSP at its best!'); end; end.

That and now outright crashes while the 'calculating..' popup appears to freeze up.

An installer overwrote changes I made to a component. During app compile the Error was clearly marked (nice), but after Reverting to my Git version the Error was still there. How does one solve this? Do you have to reload the project again?

FYI: Switching configuration back and forth refreshes CodeInsight.

THEY try and lull you into a sense of security, then when you deploy.. 🙂

As I read that its for Linux and Browsing path only:

Nope, all my Builds are clean. I figured out there was an issue due to that a couple of years ago and built a 'clean.cmd' that is triggered via 'Build Tools' I have not, because that is exactly what I was trying not to do. Sure seems that making a change then undoing it is the only way to force a Refresh at this point..

Sure, that's how the Error shows up because it parses all on opening and coding..