Handling issue with quick fixes.

[Former Member]

Hello,

while going throught the REST tutorial, I noticed a small difference in the handling between the JDT Java editor and the ADT ABAP editor. It's not much of a difference, but it's one of the small grains of sand in the gearbox

When you use a quick fix in the JDT Java editor to create a missing local variable, you can do so anywhere in the line. I prefer to complete the method call first and then immediately press Ctrl+1 while the cursor is still at the end of the line:

-- Ctrl+1 -->

As you can see, the cursor jumps to the beginning of the item to be fixed, which makes sense - I explicitly asked for a fix, so find something to fix in the vincinity.

In the ADT editor, things are a bit different at the moment:

The cursor does not move when I press Ctrl+1. Even if there is something to be fixed in the current line, I first need to navigate to the statement in question manually in order to use the quick fix.

Would it be possible to adapt the behaviour of the ADT ABAP editor in a future version so that this additional navigation step is no longer necessary?

Thanks

  Volker

[Former Member]

Hello,

while going throught the REST tutorial, I noticed a small difference in the handling between the JDT Java editor and the ADT ABAP editor. It's not much of a difference, but it's one of the small grains of sand in the gearbox

When you use a quick fix in the JDT Java editor to create a missing local variable, you can do so anywhere in the line. I prefer to complete the method call first and then immediately press Ctrl+1 while the cursor is still at the end of the line:

-- Ctrl+1 -->

As you can see, the cursor jumps to the beginning of the item to be fixed, which makes sense - I explicitly asked for a fix, so find something to fix in the vincinity.

In the ADT editor, things are a bit different at the moment:

The cursor does not move when I press Ctrl+1. Even if there is something to be fixed in the current line, I first need to navigate to the statement in question manually in order to use the quick fix.

Would it be possible to adapt the behaviour of the ADT ABAP editor in a future version so that this additional navigation step is no longer necessary?

Thanks

  Volker

[Former Member]

Hi,

I totally agree. I often find it cumbersome, to navigate exactly to the part in the line, where I can execute the quick fix.

@Volker as a workaround for most of these issues, you can quickly navigate to the marked parts in your code using CTRL - , (backward navigation) and CTRL - . (forward)

[michael_gutfleisch]

Hi Volker,

we will try to change this, but we cannot promise right now 😉

By the way: Do you know the quick assist "Assign statement to new variable?

You can trigger it on a a statement like

get_name( ).

which results in

DATA new_variable TYPE string.

new_variable = get_name( ).

This already works inside the entire statement and even behind the "."

Regards,

Michael

[ThFiedler]

Hi Volker,

good news for you. Today I have already seen the new behavior of the quick fix in our sprint review meeting. Will be part of the next released AIE client next year.

Merry Christmas and a happy new year.

Regards,

Thomas.

[Former Member]

Hi Thomas,

happy new year and thanks a lot for this information!

Best regards

  Volker