Hi experts!
Can any body suggest me some solutions or cause of the problem?
https://github.com/mkhan3189/dotCodeFx/issues/10
It related to
https://github.com/mkhan3189/dotCodeFx/blob/master/src/helpers.h#L101
All I am trying to do is delete all the tracked classes. Please see new()
operator
On 10/03/2012 12:10 AM, Andreas Holzammer wrote:
I can only add that the reported physical dpi for windows are not the
real physical. They report what the user has set in windows for it, or
better to say it defaults to 96 dpi. There seems to be no api from
windows to find out the actual api,
On 10/02/2012 01:58 PM, Atlant Schmidt wrote:
Samuel:
Specifying that all characters must be 5mm in physical height is
typically not what a UI wants in any case, since different types of
displays (mobiles / tablets, computer monitors, and TVs) are typically
viewed at different distances.
No worries. Development is still going strong. It just happens that the people
that are involved in component development are the very same people trying to
push a Qt 5.0 release out of the door right now. This obviously means a bit
less focus on new feature development while the release is
how dotCodeFX is related to Qt development? (hint: nohow)
P.S. using Windows Task manager to confirm some memory leaks is seems
quite stupid to me ;)
regards,
Konstantin
2012/10/3 Majid Khan mkhan3...@gmail.com:
Hi experts!
Can any body suggest me some solutions or cause of the problem?
P.S. using Windows Task manager to confirm some memory leaks is seems
quite stupid to me ;)
Why that's my favorite tool for detecting memory leaks of windows.. if the
numbers keep growing you have a problem.
Morten
___
Development mailing list
On 3 October 2012 12:12, Samuel Rødal samuel.ro...@digia.com wrote:
On 10/02/2012 01:58 PM, Atlant Schmidt wrote:
Samuel:
Specifying that all characters must be 5mm in physical height is
typically not what a UI wants in any case, since different types of
displays (mobiles / tablets, computer
Help by offering your opinion on:
* Does the example have a meaningful purpose? Or is the feature it
demonstrates deprecated or obsolete in Qt 5?
* Does it follow Qt 5 best practice / recommended way of doing things?
* Are the comments, text strings, README, etc up to date?
* Is the example
Hi Shawn,
On Wed, Oct 3, 2012 at 2:24 PM, Shawn Rutledge
shawn.t.rutle...@gmail.com wrote:
I've been working on this patch to make QScreen properties more
complete and remove the hard-coded 72 DPI:
https://codereview.qt-project.org/#change,36121
I was surprised to find that if I ask OS X for
You can use \quotefromfile, \skipto, \printuntil, etc
http://doc-snapshot.qt-project.org/qdoc/07-0-qdoc-commands-includingexternalcode.html#quotefromfile-command
martin
On Oct 3, 2012, at 2:29 PM, Sorvig Morten wrote:
Help by offering your opinion on:
* Does the example have a meaningful
Hi all,
We are preparing to release a repackaged version of Qt 4.8.3 with Digia
copyrights (Qt 4.8.3-1) very soon. The Qt 4.8.3-1 contains the same
functionality as the Qt 4.8.3 release with copyright changes from Nokia to
Digia (sha1 has not been changed). This copyright change is a legal
Hi,
On 3 October 2012 17:09, Salovaara Akseli akseli.salova...@digia.com wrote:
We are preparing to release a repackaged version of Qt 4.8.3 with Digia
copyrights (Qt 4.8.3-1) very soon. The Qt 4.8.3-1 contains the same
functionality as the Qt 4.8.3 release with copyright changes from Nokia to
On quarta-feira, 3 de outubro de 2012 17.31.41, Giuseppe D'Angelo wrote:
Hi,
On 3 October 2012 17:09, Salovaara Akseli akseli.salova...@digia.com
wrote:
We are preparing to release a repackaged version of Qt 4.8.3 with Digia
copyrights (Qt 4.8.3-1) very soon. The Qt 4.8.3-1 contains the
So the problem went away after a reboot during weekend and the bug is
thus marked as invalid.
However another commenter indicated it's happening on his Mac too. I
just retried the example and sure enough the problem shows up again.
Can people running Qt 5 on Mac try the example in the report
Thiago Macieira wrote:
Can't you push a commit on top of 4.8.3 that updates the license
files, and tag that commit 4.8.3-1?
If we do that, we should just call it 4.8.4.
Isn't that what happened also when Nokia bought Qt? 4.4.3 was technically a
rebranding release. I think that is what
Can't you push a commit on top of 4.8.3 that updates the license
files, and tag that commit 4.8.3-1?
If we do that, we should just call it 4.8.4.
Isn't that what happened also when Nokia bought Qt? 4.4.3 was technically a
rebranding release. I think that is what should happen now as well.
On quarta-feira, 3 de outubro de 2012 19.00.14, Turunen Tuukka wrote:
Can't you push a commit on top of 4.8.3 that updates the license
files, and tag that commit 4.8.3-1?
If we do that, we should just call it 4.8.4.
Isn't that what happened also when Nokia bought Qt? 4.4.3 was
Thus I think we have two options with the 4.8.3-1:
1. Include the copyright change and MinGW fix
2. Include only the copyright changes and fix MinGW in the next patch
release
3. Call it 4.8.4 and accept that it can not be fetched from the
repository
4. Call it 4.8.4, apply the copyright
Hi there,
On Wed, Oct 03, 2012 at 07:49:38PM +, Turunen Tuukka wrote:
Thus I think we have two options with the 4.8.3-1:
1. Include the copyright change and MinGW fix
2. Include only the copyright changes and fix MinGW in the next patch
release
3. Call it 4.8.4 and accept that
Can you please suggest the best tools that Qt community use for memory leak
detections?
Greatly appreciated. Thanks
On Wed, Oct 3, 2012 at 10:19 PM, Sorvig Morten morten.sor...@digia.comwrote:
P.S. using Windows Task manager to confirm some memory leaks is seems
quite stupid to me ;)
Why
On quinta-feira, 4 de outubro de 2012 09.04.21, Majid Khan wrote:
Can you please suggest the best tools that Qt community use for memory leak
detections?
valgrind, valgrind, valgrind
For Windows users, there are commercial tools:
Intel Inspector XE (part of the Parallel Studio XE)
Why that's my favorite tool for detecting memory leaks of windows.. if the
numbers keep growing you have a problem.
It does not detect leaks. It reports memory claimed by process.
So its usage is limited.
It is not useless, but you can't base memory leaks claims on the
information it provides.
22 matches
Mail list logo
