We have many functions that look like this:

function TQuerEbenheit_EA_Daten.Abscissa: TAbscissa;
begin
Result.AssignKm(Messkm);
end;

TAbscissa is an extended record with mutliple AssingXxx methods that initialize its value. So the result is actually initialized. I haven't got a good idea how to solve this. Maybe instead of an AsssignXxx method I should change this to a constructor call with an assignment?

Result := TAbscissa.CreateFromKm(Messkm);

But that would add the overhead of creating an additional record and assigning it to result. Not much of an overhead. The problem is more that we would have to rewrite lots of code.

Right now FixInsight does not satisfy it's name - a proper name would rather be AnalysisInsight for the current feature set. Med term FixInsight should start providing fixes for one or the other convention/rule violation. A start could be fixes for C109 and W514.

I'd like to be able to de-select the reports I never want enabled, and then choose "Make this my default selection" for any new report.

In order to run FixInsight for a specific unit a have to make this unit the active unit, have to call FixInsight from the popupmenu for the project node and have to choose "Analyze current unit only" from the dropdown menu of the "Run" button. That is a bit cumbersome. The module nodes should have a FixInsight menu item that shows the FixInsight settings dialog with a "Run for current unit" button.

It would be nice to have a method for adding an ignore comment for the warning FixInsight reports on a particular line. E.g. if the for loop variable is not inside the loop, and that's not an error, have a context menu for the warning that opens a dialog for adding a user comment (pre filled if possible) and then adds a
//FI:W528 - <user comment here>
to the line in question.

New in FixInsight 2015.11 in contrast to 2015.10 is C109 for "BooleanValue = False" like in the following function:

function TestC109False(AValue: Boolean): Boolean;
begin
  Result := AValue = False;
end;

This comparison is not unnecessary, because when removing "= False" one will get the opposite result. However the style is bad and for now a different text for the "= False" case, that suggests using "not", would be sufficient.

Currently there is only one menu item that calls the FixInsight dialog. This dialog has multiple functions:
* Configure FixInsight
* Run FixInsight on the project
* Run FixInsight on the current unit

I already complained about the last one, but it's equally inconvenient that the only way to change the configuration is to run FixInsight afterwards. Consider this:
I find that there is a 3rd party unit that generates many warnings and I decide that I won't bother checking this code in the future because I am not going to fix it anyway. So I want to add this unit to the exception list. How do I do that? If I open the dialog, I must run FixInsight afterwards in order for the configuration change to be saved. But I am in the process of going through the list of warnings, which will be changed when I run it again. At minimum I lose the current position in the list I was looking at.