Author Topic: References not working correctly in C/C++ code  (Read 3132 times)

rsadeh

  • Junior Community Member
  • Posts: 9
  • Hero Points: 0
References not working correctly in C/C++ code
« on: September 01, 2014, 09:42:31 AM »
Hi,
I'm trying the new v19 beta1 in Linux 32bit (Fedora 20) with a fairly large workspace with mixed C and C++ code.
When I invoke reference for a symbol (ctrl-/) and then traverse them with ctrl-g what I see is that the traversal is correct for occurences within the same file where I initiated the operation but once other files are visited then the cursor is not placed correctly.
This, of course, works correctly in v18.

Clark

  • Moderator
  • Senior Community Member
  • *
  • Posts: 6884
  • Hero Points: 530
Re: References not working correctly in C/C++ code
« Reply #1 on: September 01, 2014, 01:17:46 PM »
This is fixed in the next beta

rsadeh

  • Junior Community Member
  • Posts: 9
  • Hero Points: 0
Re: References not working correctly in C/C++ code
« Reply #2 on: September 08, 2014, 07:52:35 AM »
References are indeed fixed but "find symbol" is still not working.
Also, launching "secondary" windows (e.g. ctrl-shift-B to see all buffers) opens up the new windows with the wrong decoration (on my Fedora 20).
Thanks.

Rodney

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 798
  • Hero Points: 54
Re: References not working correctly in C/C++ code
« Reply #3 on: September 08, 2014, 10:42:33 AM »
What does "wrong decoration" mean?

++rodney

rsadeh

  • Junior Community Member
  • Posts: 9
  • Hero Points: 0
Re: References not working correctly in C/C++ code
« Reply #4 on: September 08, 2014, 10:53:15 AM »
Wrong decoration means that the window's title and buttons (minimize/maximize/close) does not look like the desktop-environment dictates (KDE in my case). The main SlickEdit windows is ok but looks like any other window that I launch (ctrl-shift-B, ctrl-shift-N) has a different title and buttons style.
In addition, if I try to dock them they trigger the new "windows-group" mechanism which is very inconvenient.
Thanks.