You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your library is awesome, but I had some problems when using it with Qt. Indeed, one of your function is called "emit", the problem is that in Qt, this is a keyword, so I had to change the name of this function in you source files (well, I just called it emitt xD).
You should rename it to avoid conflicts.
Regards,
Rodolphe Fouquet.
The text was updated successfully, but these errors were encountered:
That function name attempts to match the conventions of the socket.io, so i'd prefer to keep it as emit if possible.
I'm not really familiar with Qt, but does it #define any constants to indicate that it's being used? If it does, I can add in a section that defines an identical function of a different name. Or if not, we'll just have to add an option to use a function with a different name.
For those who may have this issue nowadays, I met similar issue recently.
I'm using Visual Studio 2015. The code won't compile successfully using this lib with Qt.
The reason is that Qt defined emit for event emitting which conflict with this lib.
Here is the solution I found, which temporarily disable this macro and restore it later :
Hello,
Your library is awesome, but I had some problems when using it with Qt. Indeed, one of your function is called "emit", the problem is that in Qt, this is a keyword, so I had to change the name of this function in you source files (well, I just called it emitt xD).
You should rename it to avoid conflicts.
Regards,
Rodolphe Fouquet.
The text was updated successfully, but these errors were encountered: