Hi guys,
I'm currently doing a bit of refactoring using the latest Nightly (4639). There is a small thing that I hope can be improved. If gcc reports a compilation error due to accessing private/protected class members it shows up like this:
..\lib3DHelp/RCT3Structs.h:166: error: 'wxFileName cFlexiTextureFrame::Texture' is private
C:\Development\svn\RCT3 Importer\src\RCT3 Tool\wxdlgTexture.cpp:186: error: within this context
C::B reacts by juming to the first error instance, which is the member declaration. The trouble is that usually you have a good reason to declare something private, so (I think) what usually needs fixing is the second ('within this context') error. Could CB get a special handling for this and jump to the second instead?
Maybe this is not an issue for many people, but if you try to refactor what originally was a simple struct into a sensible class it tends to make you mad
