Author Topic: RC1: C++ next line indent/cursor placement  (Read 2247 times)

mklein

  • Community Member
  • Posts: 90
  • Hero Points: 2
RC1: C++ next line indent/cursor placement
« on: October 30, 2014, 05:19:27 pm »
Hi,

Starting in RC1 I'm seeing some strangeness of where the editor places my cursor when I hit enter and move to the next line. This doesn't always happen, but sometimes the cursor placement seems almost random and not having anything to do with my editor settings (Google coding style).

This is not super easy to come up with a self-contained repro for but I will try.

Are there any known issues in this area that might have changed between B6 and RC1?

Thanks,
Matt

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1682
  • Hero Points: 142
Re: RC1: C++ next line indent/cursor placement
« Reply #1 on: October 30, 2014, 05:37:50 pm »
The only change I see in that time frame  has to do with calculating the indent for when you hit enter inside of a C++ lambda.  For the sake of paranoia, I'll double check the code that triggers that to make sure that can't get triggered in other places.


mklein

  • Community Member
  • Posts: 90
  • Hero Points: 2
Re: RC1: C++ next line indent/cursor placement
« Reply #2 on: October 30, 2014, 05:39:07 pm »
FWIW, there are lambdas in the general areas where this appears to happen.

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1682
  • Hero Points: 142
Re: RC1: C++ next line indent/cursor placement
« Reply #3 on: October 30, 2014, 05:47:17 pm »
Ack, I think I've reproduced it.  Bad behavior near a lambda that's in a function call.  Looking in to it.

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1682
  • Hero Points: 142
Re: RC1: C++ next line indent/cursor placement
« Reply #4 on: October 30, 2014, 06:54:47 pm »
Fixed for the next build or the first hotfix.  I also found and fixed a related bug with line splits inside of lambda expressions.    Thanks for the report.