On 10/31/2019 3:07 AM, Giuseppe D'Angelo wrote:
Il 31/10/19 01:55, Bob Hood ha scritto:
I'm on Windows using Qt Creator 4.6.2.
Apart from MSVC working on porting ASAN, there's a memory error detector
available as part of Intel Studio.
To me, valgrind/ASAN is still a _huge_ reason to prefer
Il 31/10/19 01:55, Bob Hood ha scritto:
I'm on Windows using Qt Creator 4.6.2.
Apart from MSVC working on porting ASAN, there's a memory error detector
available as part of Intel Studio.
To me, valgrind/ASAN is still a _huge_ reason to prefer Linux
development. If you can, get a testcase an
Am Wed, 30 Oct 2019 18:55:04 -0600
schrieb Bob Hood :
> (Sorry for the slow reply. F#@$ing Comcast decided yesterday that all my
> mailing list traffic was Spam.)
>
>
> On 10/30/2019 5:17 AM, Giuseppe D'Angelo via Interest wrote:
> > On 30/10/2019 01:47, Bob Hood wrote:
> >> When I enter the
(Sorry for the slow reply. F#@$ing Comcast decided yesterday that all my
mailing list traffic was Spam.)
On 10/30/2019 5:17 AM, Giuseppe D'Angelo via Interest wrote:
On 30/10/2019 01:47, Bob Hood wrote:
When I enter the constructor, I have a specific ‘this’ pointer that has the
provided ‘siz
On 30/10/2019 01:47, Bob Hood wrote:
When I enter the constructor, I have a specific ‘this’ pointer that has
the provided ‘size’ argument placed into its ‘entity_size’ member.
However, when Qt subsequently invokes the boundingRect() override
function, it’s an entirely different ‘this’ instance
I’m sure I’m being dense here, but I’m confused about why my QGraphicsItem
subclass is being called with a different instance when the overrides of the
boundingRect() and paint() functions are being called. Here’s the code…
Header:
|class Entity : public QGraphicsObject { Q_OBJECT public: expl
