On Fri, 21 Mar 2014 10:55:10 +0100
André Somers wrote:
> Constantin Makshin schreef op 21-3-2014 04:46:
> > I don't see anything bad even in redefining the "qApp" macro itself
> > (inclusion guards in Qt headers will protect your redefinition from
> > being reverted) instead of inventing your "my
Constantin Makshin schreef op 21-3-2014 04:46:
I don't see anything bad even in redefining the "qApp" macro itself
(inclusion guards in Qt headers will protect your redefinition from
being reverted) instead of inventing your "myApp" one.
I think it may be confusing to do so. The meaning of qApp w
I don't see anything bad even in redefining the "qApp" macro itself
(inclusion guards in Qt headers will protect your redefinition from
being reverted) instead of inventing your "myApp" one.
On 03/20/2014 10:58 PM, Andrej Kacian wrote:
> Hello all,
>
> I was wondering, if I subclass QApplication
Hello all,
I was wondering, if I subclass QApplication for my program, is it a good idea
to just copy and adjust the definition of "qApp" macro if I want to use a
similar macro to refer to my subclass from anywhere?
E.g.:
#if defined(myApp)
#undef myApp
#endif
#define myApp (static_cast(QCoreAppl
