Delphi 10.4.1 code navigation - Cursor is vanished

[RonaldK 18]

Updated to Delphi 10.4.1

When using the code navigation [STRG][Shift] Cursor up/down the cursor vanish and I cant see the text cursor.

Any settings needed?

 

[Lars Fosdal 1730]

Is this to navigate between interface and implementation for a class method?

[RonaldK 18]

20 minutes ago, Lars Fosdal said:

Is this to navigate between interface and implementation for a class method?

Yes. After any navigation the source code cursor isn't visible.

I can't see the actual line without the cursor. I have to press a cursor key to get it back.

[Lars Fosdal 1730]

I haven't seen that specific problem, but I have some units where Ctrl+Shift+Arrow up/down simply refuses to work in 10.4.1 as well as 10.3.3.

I need to try to make a minimal example and report it.

[Lars Fosdal 1730]

See comments #1
Ctrl+Shift+ArrowUp/Down does not work.
Seems to be due to typed constant.
 

See comments #2:
Broken class completion, seemingly due to same cause as #1.

 

    program SydneyCodeNav;

    {$APPTYPE CONSOLE}

    {$R *.res}

    uses
      System.SysUtils;

    type
      TRec = record
        a: Integer;
    //     procedure Test;  // #2 Uncomment line and press Ctrl+Shift+C to complete code
      end;

      TMyObject = class
      const
        TR:TRec = (a:1);
      private
        procedure InternalTest; // #1 Place cursor here, try Ctrl+Shift+ArrowDown does not work
      public
        procedure Test;
      end;

      TUnrelated = class
    //    procedure Unrelated; // #2 Uncomment line and press Ctrl+Shift+C to complete code
      end;

    { TMyObject }

    procedure TMyObject.InternalTest;
    begin
      Writeln('InternalTest'); // #1 Place cursor here, Ctrl+Shift+ArrowDown
    end;

    procedure TMyObject.Test;
    begin
      Writeln('Test'); // #1 Place cursor here, Ctrl+Shift+ArrowDown does not work
      InternalTest; // Ctrl-Clicking InternalTest works
    end;

    procedure Test;  // Chtrl+Shift+ArrowUp/Down works here
    var
      o: TMyObject;
    begin
      o := TMyObject.Create; // Chtrl+Shift+ArrowUp/Down works here
      try
        o.Test;
      finally
        o.Free;
      end;
    end;

    begin
      try
        try
          Test;
        except
          on E: Exception do
            Writeln(E.ClassName, ': ', E.Message);
        end;
      finally
        Write('Press Enter: ');
        Readln;
      end;
    end.

 

[RonaldK 18]

Seems to be another problem of general navigation.

In my case the navigation works but the cursor is not visible or painted.

 

After Crtl+Shift Up/down and navigate to the left or right, the cursor is painted twice:

 

This does not happen in a new Windows application.

Maybe using some other units cause this. Try to find which unit it is.

 

I'm using DevExpress components, maybe not fully fixed:

https://supportcenter.devexpress.com/ticket/details/t897104/autocomplete-not-working-on-d10-4-after-add-tcxbutton-or-other-dx-component

https://quality.embarcadero.com/browse/RSP-29674

 

Ronald

 

 

 

[Lars Fosdal 1730]

Found a somewhat related case to my issue in QP:
https://quality.embarcadero.com/browse/RSP-28514
Added my comments to it.

[Lars Fosdal 1730]

5 minutes ago, RonaldK said:

In my case the navigation works but the cursor is not visible or painted.

Have you tested without extra IDE extensions?

[RonaldK 18]

8 minutes ago, Lars Fosdal said:

Have you tested without extra IDE extensions?

Yes. I'm using no IDE extensions.

[RonaldK 18]

Is there an option to disable the new LSP and using the old one?

[Stano 139]

[RonaldK 18]

Ok. Thanks.

Doesn't fix the problem.

[balabuev 97]

On 9/9/2020 at 9:51 AM, Lars Fosdal said:

Seems to be due to typed constant.

 

I have another one (more exotic) example:

unit Unit1;

interface

type
  TFoo = record
    X: set of (s1, s2, s3);
    Y: record
         Z: (e1, e2, e3);
       end;
  end;

  TBar = class
  private
    procedure P; // Ctrl+Shift+C does not work!
  end;

implementation

end.

 

Edited January 7, 2021 by balabuev

[Lars Fosdal 1730]

I think code completion in 10.4.1 is still using the old parser, hence it still misbehaves around certain constructs.
@balabuev You should add your example to one of the existing code completion issues in QP - or register a new issue.

[balabuev 97]

20 minutes ago, Lars Fosdal said:

I think code completion in 10.4.1 is still using the old parser, hence it still misbehaves around certain constructs.

Agree, and I've added a comment to QP. But, my point is that code constructs, I've shown, are veeeery old too.