Community
Participate
Working Groups
One of the things, that we would like to avoid, is that customers see any processor specific information in CDT. For example, they should not see register values. The reason for that is that we will probably change the processor family used on our boards and we do not want the customers to base their solutions on any processor-specific information. There are also some security consideration. Anyway, I tried to disable these features in my plugin. For registers view, I tried to define my own TargetConfiguration subclass and there I defined supportsRegisters() and supportsRegisterModification() to return false. But it seems to me that these flags are not taken into account by CDT. Therefore, I can still see the values of registers in the registers pane. I think this is a bug and Mikhail Khodjaiants confirmed it.
Fix for "supportsRegisterModification" submitted. As for "supportsRegisters" the UI-related API has to be changed to affect the register groups actions.