That means you can then dynamically find, and get call signatures and through Qt's signals/slots, invoke via text an object.
path from top most application node to the bottom:
That means that every QObject in the entire application (or at least, the top most window) has (almost always) a unique. For most cases, that makes it (typically) unique. You can set it programmatically, or set it in the IDE using Qt Designer, or have it be auto-assigned by Qt Designer. In Qt, every QObject derived instance has a name. For an advanced user, it's a good reference for situations where you have a large semi-dynamically constructed interface or you need reflection style programming but are in C++. For beginners, it provides direct insight as to what really goes on in signals and slots. This article exposes some of the underlying things that Qt uses for object model manipulation and threading.
