The Next Generation of 2D Roleplaying Games
http://elysianshadows.com/phpBB3/
That's correct. Qt has a signal/slot implementation that it gets to work via a separate pre-processor and some fancy C preprocessor macros. Qt is a good library, but I'm curious the effect of using Qt's signals/slots on the overall size and performance of a program.XianForce wrote:QT SIGNAL and QT SLOT... That's just a signal/slot implementation, isn't it...?
Yeah, it just confuses me because Falco said:Ginto8 wrote:That's correct. Qt has a signal/slot implementation that it gets to work via a separate pre-processor and some fancy C preprocessor macros. Qt is a good library, but I'm curious the effect of using Qt's signals/slots on the overall size and performance of a program.XianForce wrote:QT SIGNAL and QT SLOT... That's just a signal/slot implementation, isn't it...?
But we aren't doing any signal/slots bullshit to implement this.
Probably pretty fucking hefty. It's more than worth it, when every class within a GUI application uses the paradigm, but for a single subsystem, as has been proposed here, it would be a ridiculous amount of overhead (oh, and now you get to use an additional layer of preprocessing for one class).Ginto8 wrote:That's correct. Qt has a signal/slot implementation that it gets to work via a separate pre-processor and some fancy C preprocessor macros. Qt is a good library, but I'm curious the effect of using Qt's signals/slots on the overall size and performance of a program.XianForce wrote:QT SIGNAL and QT SLOT... That's just a signal/slot implementation, isn't it...?
Okay haha. I thought for a second you were saying that you used QT SIGNAL and QT SLOT to call those methods, and I was a little confused for a second. Thanks for the clarificationGyroVorbis wrote:I was drawing an analogy to the fact that we implemented the exact same functionality with a simple abstract base class and some virtual methods...
.