[Connect SDK update 5] Errors when including PointCloudApi.h

Hi,

My system is windows 7, VS 2013, VS 2015, NO clr support

I get same 11 errors, VS2013 and VS 2015 when including PointCloudApi.h

Same errors has occurred in update 1,2,3 and 4

Error list:

Error 9 error C2039: 'OrientedBoxCR' : is not a member of 'Bentley::DgnPlatform'
Error 12 error C2039: 'OrientedBoxCR' : is not a member of 'Bentley::DgnPlatform'
Error 14 error C2061: syntax error : identifier 'IPointCloudChannelVectorCR'
Error 10 error C2061: syntax error : identifier 'OrientedBoxCR'
Error 13 error C2061: syntax error : identifier 'OrientedBoxCR'
Error 11 error C2061: syntax error : identifier 'PointCloudChannelId'
Error 6 error C2061: syntax error : identifier 'PointCloudPropertiesCR'
Error 8 error C2065: 'Xyz' : undeclared identifier
Error 15 error C2535: 'Bentley::IPointCloudQueryBuffersPtr Bentley::PointCloud::IPointCloudDataQuery::CreateBuffers(UInt32,UInt32)' : member function already defined or declared
Error 7 error C2653: 'PointCloudChannelId' : is not a class or namespace name
18 IntelliSense: cannot open source file "_config-eccp.h"

Any suggestions?

thanks

Nenad

Parents
  • Did you try to analyse header files? Your error list does not provide enough information, because it's not clear in what header file(s) the errors arised. PointCloudApi.h is an "entry point" only that includes other header files.

    Also, did you try to include PointCloudClipHandler.h? As I wrote and Jon confirmed, OrientedBoxCR is defined in this header. Did you check the header file is properly included in the place where error is reported? The header file seems fine to me, but to have and use some testing code is always better.

    Unknown said:
    I get same 11 errors, VS2013 and VS 2015 when including PointCloudApi.h

    Why do you mention VS2013 when reporting error for Update 5? It's a bit confusing and not relevant for the reported problem, because only VS2015 is supported by update 5 SDK.

    Unknown said:
    Any suggestions?

    Ask in a better way. For example I found out in this post Artur confirmed the bug was reproduced and logged as Defect # 641666. Why you don't ask directly whether Defect # 641666 has been solved in Update 5 SDK?

    With regards,

     Jan

  • Hi,

       "Did you try to analyse header files?"

    Yes I did. As I wrote, errors have occurred in all updates and I have tried and analyzed everything I could think off.

         "Also, did you try to include PointCloudClipHandler.h? "

    Yes, I did and as result I got not 11 but 24 errors.

    "Why do you mention VS2013 when reporting error for Update 5? It's a bit confusing and not relevant for the reported problem, because only VS2015 is supported by update 5 SDK."

    As I mentioned before, these errors occurred from update 1 to update 5. Previous updates were supported by VS2013

    "Ask in a better way. For example I found out in this post Artur confirmed the bug was reproduced and logged as Defect # 641666. Why you don't ask directly whether Defect # 641666 has been solved in Update 5 SDK?"

    I did ask in my post if anybody have list/link  of fixed issues in SDK for Connect update 5 (10050040). 

    But even with that list and answer from Artur , how can I be sure that this is not a new bug? Or maybe  Defect # 641666 is just partially fixed?

    thanks

    Nenad

Reply
  • Hi,

       "Did you try to analyse header files?"

    Yes I did. As I wrote, errors have occurred in all updates and I have tried and analyzed everything I could think off.

         "Also, did you try to include PointCloudClipHandler.h? "

    Yes, I did and as result I got not 11 but 24 errors.

    "Why do you mention VS2013 when reporting error for Update 5? It's a bit confusing and not relevant for the reported problem, because only VS2015 is supported by update 5 SDK."

    As I mentioned before, these errors occurred from update 1 to update 5. Previous updates were supported by VS2013

    "Ask in a better way. For example I found out in this post Artur confirmed the bug was reproduced and logged as Defect # 641666. Why you don't ask directly whether Defect # 641666 has been solved in Update 5 SDK?"

    I did ask in my post if anybody have list/link  of fixed issues in SDK for Connect update 5 (10050040). 

    But even with that list and answer from Artur , how can I be sure that this is not a new bug? Or maybe  Defect # 641666 is just partially fixed?

    thanks

    Nenad

Children