Is this an official Qt5 github resource ?
-
https://github.com/GarageGames/Qt
Deep in the bowels of thus doc is "class " Q_D" still eluding definitions / source.
Looking for a link / relations between QT Bluettoth and blueZ stack.
Am I in wrong pew / even right church?
Cheers -
https://github.com/GarageGames/Qt
Deep in the bowels of thus doc is "class " Q_D" still eluding definitions / source.
Looking for a link / relations between QT Bluettoth and blueZ stack.
Am I in wrong pew / even right church?
Cheers@AnneRanch This is the whole Qt Project git repository
Beyond the Qt framework itself, you'll find code for several other modules, tools and experimental stuff.
In addition, you can browse online the Qt source code here as well:
-
Just to add - the
Q_DandQ_Qmacros are part of the D-Pointer design pattern implementation of Qt.The details on what it is and what it does are in this wiki article: D-Pointer.
In short it's a mean to achieve binary compatibility between Qt versions by keeping private implementation details away from the public class interface and linking them through a Data Pointer member.Q_Dis just a shorthand to retrieve that data pointer inside member implementations. -
Just to add - the
Q_DandQ_Qmacros are part of the D-Pointer design pattern implementation of Qt.The details on what it is and what it does are in this wiki article: D-Pointer.
In short it's a mean to achieve binary compatibility between Qt versions by keeping private implementation details away from the public class interface and linking them through a Data Pointer member.Q_Dis just a shorthand to retrieve that data pointer inside member implementations.@Chris-Kawa said in Is this an official Qt5 github resource ?:
Just to add - the
Q_DandQ_Qmacros are part of the D-Pointer design pattern implementation of Qt.The details on what it is and what it does are in this wiki article: D-Pointer.
In short it's a mean to achieve binary compatibility between Qt versions by keeping private implementation details away from the public class interface and linking them through a Data Pointer member.Q_Dis just a shorthand to retrieve that data pointer inside member implementations.Aha, just what I been looking for - the actual link to "blueZ" .
Now I have complied bluez as "libblueman" which still does not tell how "Bluetooth Manger" implements "Remove" bluetooth device . But getting closer.I am beginning to realize that the whole mess is in simple logic - once the device is discovered who would need to discover it again?
The question is - how does Qt Bluetooth STILL posts SIGNAL "device detected " - what info parameter is used - if that is the case. I'll keep digging.
But that is a subject of another post, do not let me mix it up any more.
Cheers
