Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Favorites |
infavorites:mine infavorites:1234 |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
0
votes
2answers
:
You should always allocate qobjects on the heap
We had a bit of a discussion about this. Frankly I was shocked, as I operated under the idea that:
Fear QObject pointers, and only use them … allocate QObjects to the heap. I think under the idea that while you could do it fairly safely using the stack, there is no good reason why you would not want a QObject on the heap, given how easy …
asked Dec 13 '18 by Akiva
7
votes
6answers
objects large enough to benefit from delegating them to the heap.
At most; my largest object would probably be a QString of maybe a million characters.
However, I just assume it is not large enough to … benefit from the heap; How should I go about estimating whether an object I have created is large enough to benefit from being turned into a pointer?
…
asked Nov 10 '16 by Akiva
