In C++, you can acquire a class object or your class item can assume the qualities of another class object. Consequently, there is an “is-a” or a “has-a” relationship that is conceivable with each class object made. Picture this then: A button inside a button, inside a button, inside a button, etc…
Assuming the center button makes the external button connected with it (and it can do as such, in three distinct modes – private, public and secured), then, at that point, it just makes sense, to feel free to report that relationship. Contingent upon how their legacy relationship was labeled, you should list down what is private information (factors and works) to the external button.