Thanks a load Kamrann! I can understand exactly what this issue is now. I’ve actually had issues with this kind of thing elsewhere, only with the opposite effect (incorrectly displaying properties in C++ component, but works fine on blueprint added one of the same class).
FML 
thanks for the info though, I’ll have a quick check and see what happens if its added on a C++ version. Strangely enough, I think it might be OK as we’re likely to be using these classes on C++ based components. I was just testing on a blueprint version to see if I could get it working.