编译器优化以减少可执行代码的字节数(Compiler optimization to reduce bytes of executable code)

 首先，对象实例的大小本身并不重要。 该类应设计为具有单一责任，如果需要540字节的数据，那么就是这样。 
 
 但是，540字节是一个非常大的数字。 这是135个整数或指针。 这就像22 std::vector s。 我很难想象单个责任区域可能需要这么多物体。 但同样，尺寸本身不是问题。 问题是如果你的班级负责的比他们应该做的更多。 
 
 
 
 我在想，既然不是所有的窗口都有子节点，我可能会将处理子节点的代码（它的对齐等）拆分成一个单独的类并指向它。 文本，图标和滚动等也是如此。 
 
 
 听起来你基本上只有一个EverythingUI类。 是的，这是糟糕的设计。 由于这个原因拆分它。 处理文本与处理图标或滚动或无关......将它们放在不同的类中。 

First, the size of an object instance in itself doesn't really matter. The class should be designed to have a single responsibility, and if that requires 540 bytes of data, then so be it.
 
However, 540 bytes is a unusually big number. It's 135 integers or pointers. It's something like 22 std::vectors. I have a hard time imagining that so many objects can be required for a single area of responsibility. But again, the size itself isn't the problem. The problem is if your class is responsible for more than it should.
 
 
 
I was thinking, that since not all windows have children, I might split parts of the code that handles having children (its alignment etc) into a separate class and have a pointer to it. Same goes with texts, icons, and scrolling etc.
 
 
It sounds like you've basically got a single EverythingUI class. And yes, that is bad design. Split it up for that reason. Handling of text has nothing to do with handing of icons or scrolling or... Put them in different classes.