Visual bug: using column marking and indenting show artifacts

[Claus Pedersen]

I have two lines of code:
a:=
b:=

I use column marking to mark the two characters := in each line (4 characters are now marked). I use Tab or Ctrl-I twice to indent the block (I have a tab-size of two). The screen now looks like this:
a : :=
b : :=

The two 'ghost' colons in the middle are just a visual flaw, they do not persist, but they seem a little strange in the editing process.

And BTW, this leaves a 'hole' in the IDE, when using Alt-Tab to shift applications, a bit of graphic from the other application can be seen in the editor. This also disappears again when editing continues.

I am using version 9.0.5

 

[Marco Kalter]

I cannot reproduce this. Can you let me know your editor font?

 

[Claus Pedersen]

My editor font is Courier New, Regular, 10, Script Western (I believe this is the default).

The settings I have changed from default are the following:
Connection, Allow multiple connections = No
Connection, Store recent history = Yes
Connection, Store with password = Yes
Object browser, Show data types = Yes
Editor, Backspace unindents = Yes
Editor, Keyword case = Uppercase
Code assistant, Coding style = Lowercase
Backup, Disabled

I have tried to change to other fonts and font sizes, but the result is the same: there is a small artifact and a hole in the IDE.

I am using Windows XP Professional Version 2002, Service Pack 3 with a screen resolution of 1280x800 pixels on a Lenovo T61 laptop

 

[PeterW]

I have two lines of code:
a:=
b:=

I use column marking to mark the two characters := in each line (4 characters are now marked). I use Tab or Ctrl-I twice to indent the block (I have a tab-size of two). The screen now looks like this:
a : :=
b : :=

I can reproduce this. With a tab-size of three. Also on 9.0.5. Font: Bitstream Vera Sans Mono, Regular, 9.

When you indent a selected block outside the marked area, a column of characters 'sticks' on the screen. Until you clear the marked area.

 

[Marco Kalter]

A tab size of 3 and/or specific font properties does not reproduce it either. We'll check it out though.

 

[Claus Pedersen]

This flaw is still present in version 10 beta 1

 

[Claus Pedersen]

This seems to be solved in beta 5, thanks