Roger Alcindor
asked on
Code Insight not working as expected/desired with RAD Studio 10.3
I have last week installed the latest RAD Studio Rio version 10.3 and can't make code insight work properly with a Windows VCL application.
The same code works fine with RAD Studio 10.2.3 Toyo which I have installed on the same PC ( Windows 10 Professional 64 bit)
I attach two screenshots of the same code snippet showing code insight for an STL <list> template variable which shows correct members such as push_back in the RAD studio 10.2.3 IDE but something else in the RAD Studio 10.3 IDE.
I have enabled all the options in the Code insight settings and can't see why the code insight isn't working as expected (or desired).
Any comments would be appreciated.
RADStudio102.jpg
RADStudio103.jpg
The same code works fine with RAD Studio 10.2.3 Toyo which I have installed on the same PC ( Windows 10 Professional 64 bit)
I attach two screenshots of the same code snippet showing code insight for an STL <list> template variable which shows correct members such as push_back in the RAD studio 10.2.3 IDE but something else in the RAD Studio 10.3 IDE.
I have enabled all the options in the Code insight settings and can't see why the code insight isn't working as expected (or desired).
Any comments would be appreciated.
RADStudio102.jpg
RADStudio103.jpg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Just started using "classic Borland compiler" instead of Clang on RAD studio C++ builder 10.3 and there are different errors with code insight.
I will revert to yoyo 10.2.3.
You would think that these bugs would have been corrected prior to release of 10.3, the only conclusion is that they didn't notice or were in a rush to get to market and decided that the customer would put up with these errors.
I will revert to yoyo 10.2.3.
You would think that these bugs would have been corrected prior to release of 10.3, the only conclusion is that they didn't notice or were in a rush to get to market and decided that the customer would put up with these errors.
ASKER
Thanks for the comment,
Roger