Author Topic: Class window not showing all the base classes  (Read 2684 times)

rowbearto

  • Senior Community Member
  • Posts: 2335
  • Hero Points: 132
Class window not showing all the base classes
« on: February 28, 2018, 06:49:51 PM »
With attached test.cc file, in the "Class" tool window I expect to see 4 base classes for "Derived" class, but I only see 1 - see attached picture.

I'm using 22.0.2 on Linux x64 Centos 7.
« Last Edit: February 28, 2018, 06:51:36 PM by rowbearto »

Dennis

  • Senior Community Member
  • Posts: 3965
  • Hero Points: 517
Re: Class window not showing all the base classes
« Reply #1 on: February 28, 2018, 10:51:17 PM »
Reproduced.  This will be fixed in the next release.

rowbearto

  • Senior Community Member
  • Posts: 2335
  • Hero Points: 132
Re: Class window not showing all the base classes
« Reply #2 on: February 28, 2018, 11:27:42 PM »
Thanks!

Will there be another release of SE 2017? Or will need to wait for SE 2018? If another release of SE 2017 coming, do you know an approximate timeframe?
« Last Edit: February 28, 2018, 11:30:32 PM by rowbearto »

Dennis

  • Senior Community Member
  • Posts: 3965
  • Hero Points: 517
Re: Class window not showing all the base classes
« Reply #3 on: February 28, 2018, 11:33:04 PM »
At this time, this will be most likely SlickEdit 2018.

rowbearto

  • Senior Community Member
  • Posts: 2335
  • Hero Points: 132
Re: Class window not showing all the base classes
« Reply #4 on: February 28, 2018, 11:37:32 PM »
OK. Any workarounds? What specifically is causing this issue? Could the file be edited to work around it?

Dennis

  • Senior Community Member
  • Posts: 3965
  • Hero Points: 517
Re: Class window not showing all the base classes
« Reply #5 on: March 01, 2018, 04:14:39 PM »
There's a really dumb parsing error on account of the leading "::"

rowbearto

  • Senior Community Member
  • Posts: 2335
  • Hero Points: 132
Re: Class window not showing all the base classes
« Reply #6 on: August 03, 2018, 02:25:43 PM »
Just checked this with v23, looks like it is fixed! Thanks!

The real test will be when I pass this off to my colleague who identified this error and works with this code, but I'm not sure how keen he is to use a beta version, we'll see.