2016-09-08 18:50 GMT+02:00 Elvis Stansvik :
> Hi all,
>
> QSharedData and QImplicitlySharedDataPointer (QISDP) is a common
> combination used to implement implicit sharing, both in Qt itself and
> in Qt-using projects.
>
> QExplicitlySharedDataPointer (QESDP) is a cousin of QISDP with the
> importa
2016-09-08 20:33 GMT+02:00 Thiago Macieira :
> On quinta-feira, 8 de setembro de 2016 19:13:44 PDT Elvis Stansvik wrote:
>> Hm, okay. Perhaps a dumb question, but what are the consequences
>> internal vs external refcounting for me as a user of these classes?
>> Reading the docs for both of them, b
2016-09-08 20:29 GMT+02:00 Thiago Macieira :
> On quinta-feira, 8 de setembro de 2016 18:50:48 PDT Elvis Stansvik wrote:
>> QExplicitlySharedDataPointer (QESDP) is a cousin of QISDP with the
>> important difference that you have to explicitly call detach() to
>> detach from the underlying data.
>>
On quinta-feira, 8 de setembro de 2016 19:13:44 PDT Elvis Stansvik wrote:
> Hm, okay. Perhaps a dumb question, but what are the consequences
> internal vs external refcounting for me as a user of these classes?
> Reading the docs for both of them, both seem to have a thread-safe
> refcounting mecha
On quinta-feira, 8 de setembro de 2016 18:50:48 PDT Elvis Stansvik wrote:
> QExplicitlySharedDataPointer (QESDP) is a cousin of QISDP with the
> important difference that you have to explicitly call detach() to
> detach from the underlying data.
>
> QSharedPointer is Qt's own "smart pointer" to sh
2016-09-08 18:57 GMT+02:00 Konstantin Shegunov :
>
>
> On Thu, Sep 8, 2016 at 7:50 PM, Elvis Stansvik wrote:
>>
>> Hi all,
>> QSharedData and QImplicitlySharedDataPointer (QISDP) is a common
>> combination used to implement implicit sharing, both in Qt itself and
>> in Qt-using projects.
>
>
> QSh
On Thu, Sep 8, 2016 at 7:50 PM, Elvis Stansvik wrote:
> Hi all,
> QSharedData and QImplicitlySharedDataPointer (QISDP) is a common
> combination used to implement implicit sharing, both in Qt itself and
> in Qt-using projects.
>
QSharedDataPointer, the implicit part is implicit. ;)
>
> I'm curi
The device in which I’m having problems is running Android 7 (API 24)
When I use a older device running KitKat, it works.
Any ideas what this could be?
Thx,
Nuno
> On 08 Sep 2016, at 16:53, Nuno Santos wrote:
>
> Hi,
>
> From one moment to another I simply cannot have the console output of
Hi all,
QSharedData and QImplicitlySharedDataPointer (QISDP) is a common
combination used to implement implicit sharing, both in Qt itself and
in Qt-using projects.
QExplicitlySharedDataPointer (QESDP) is a cousin of QISDP with the
important difference that you have to explicitly call detach() to
Hi,
From one moment to another I simply cannot have the console output of a Qt
Android application it says:
Starting remote process. Unable to start “com.acme.org"
However the app is started…
I don’t know what to do. This has never happened before.
Does anyone has a clue?
Thanks,
Nuno_
I'm setting up a dialog that presents two side-by-side tables to the user,
allowing the user to match an item from table A with an item from table B. I'm
trying to figure out how to get both tables to use the active item selection
color, regardless of which table currently has focus.
For exampl
I too am using valgrind-3.11.0 (on Mac OS X 10.10.5), but I've never seen
that in the Application Output window. I don't usually look there when
using Memcheck.
Is there anything at all in the Memcheck panel? Sometimes if your
application crashes when using valgrind there is useful info there.
On Sep 8, 2016, at 8:18 AM, Andy
mailto:asmalo...@gmail.com>> wrote:
Ah - sorry. I can see how that's unclear (pre-coffee email).
I meant the Debug section on the left-hand side of the main window: Welcome,
Edit, Design, Debug,...
>0Then the bottom pane pops up below the editor and has a dro
André,
I've only been working with Qt for the last couple of years or so and haven't
had any formal training, so anything I'm doing is based on my interpretation of
their documentation or examples. The contents of the model itself aren't very
complex, there just happens to be the potential to h
Ah - sorry. I can see how that's unclear (pre-coffee email).
I meant the Debug section on the left-hand side of the main window:
Welcome, Edit, Design, Debug,...
Then the bottom pane pops up below the editor and has a dropdown at the
top-left - Debugger, Clang Static Analyzer, Memcheck,...
---
Hi Andy,
Could you please elaborate on step #3?
I cannot find a Memcheck option under Preferences > Debugger.
Thanks for the tips!
-Ed
Qt Creator 4.01 with Qt 5.6.1
On Sep 8, 2016, at 7:56 AM, Andy
mailto:asmalo...@gmail.com>> wrote:
Mike:
If you haven't already tried it, using Qt Creator
Mike:
If you haven't already tried it, using Qt Creator in combination with
valgrind works really well to track these kinds of things down.
The basics:
1) install valgrind (I used homebrew)
2) point Qt Creator at it in the prefs (Analyzer->Valgrind)
3) Click the Debug tab, set the tool to
On 09/07/2016 04:23 PM, Mike Jackson wrote:
We are attempting to track down a memory leak that we _think_ we have. We have
reduced our code to the point where all we do is invoke a new QWidget instance,
show() it, hide() it and then delete it. We do this in a loop 100 times. We
monitor the memory
Resending to the group instead...
On Thu, Sep 8, 2016 at 5:49 PM, Kishore J
wrote:
> Surprising! Can you test if the following code works? You should see one
> yellow circle. But do you also see 2 black and 2 blue circles? I dont see
> them here unless i uncomment the addMapItem lines
>
> /*
Op 07/09/2016 om 18:03 schreef Thompson, Adam B.:
André,
I’m just using a QStandardItemModel as the source model and a subclass
of QSortFilterProxyModel for the QTreeView mdoel. It seemed simple
enough to use QStandardItemModel for the model instead of a custom
data structure exposed via a
On Wed, Sep 7, 2016 at 11:23 PM, Mike Jackson
wrote:
> We monitor the memory use before and after the loop using OS X's Activity
> monitor. At the end of the loop there is more memory being used than before
> the loop, by about 2~3MB worth.
>
This isn't reliable. Consider the following C++ only
We are attempting to track down a memory leak that we _think_ we have.
We have reduced our code to the point where all we do is invoke a new
QWidget instance, show() it, hide() it and then delete it. We do this in
a loop 100 times. We monitor the memory use before and after the loop
using OS X'
It is odd since i tried to correct your code and then it was working
form me.
But feel free to open a bugreport with some sample code that can be
built and run to demonstrate the problem :-)
best,
Paolo
On Thu, 8 Sep 2016 10:04:27 +0530
Kishore J wrote:
> Thanks! I understand how that can be an
There were some issues with Gerrit and Jira yesterday, which are still being
looked at. Both are currently working for me for the moment.
From: Interest [mailto:interest-bounces+mitch.curtis=qt...@qt-project.org] On
Behalf Of Oleg Evseev
Sent: Wednesday, 7 September 2016 9:38 AM
To: Qt Project
24 matches
Mail list logo
