I guess, you need manually copy qmlwebkitplugin plugin to your app
bundle after exeuting macdeployqt script, then run install_name_tool to
modify the frameworks path for qmlwebkitplugin. And also, you may have to
set the plugin path for QDeclarativeEngine object in your code.
On Fri, Apr 27, 2012
Hi Alexandre,
>-Original Message-
>From: ext Alexandre Pretyman [mailto:alexandre.prety...@gmail.com]
>Sent: Friday, 27 April 2012 6:04
>To: interest@qt-project.org; Blasche Alex (Nokia-MP/Brisbane)
>Subject: Classes removed from the transition from QtMobility to QtLocation
>
>Hi Alex Bla
Hi Nikos & Scott,
IMO, both of you are right, but you are discussing two different things.
Debao
On Thu, Apr 26, 2012 at 4:13 PM, Nikos Chantziaras wrote:
> On 27/04/12 01:48, Scott Aron Bloom wrote:
>> I'm not sure if you're serious or are trolling me for fun. I *do* have
>> a sense of humor
On 27/04/12 01:48, Scott Aron Bloom wrote:
> I'm not sure if you're serious or are trolling me for fun. I *do* have
> a sense of humor, but this one I don't get :-/
>
> How is this "wrong?" You claim that if you do:
>
> QList someOtherList;
> QList< QList > list;
> list.append(som
I'm not sure if you're serious or are trolling me for fun. I *do* have
a sense of humor, but this one I don't get :-/
How is this "wrong?" You claim that if you do:
QList someOtherList;
QList< QList > list;
list.append(someOtherList);
you are able to modify 'someOtherList' through 'li
On 27/04/12 01:09, Scott Aron Bloom wrote:
> On 27/04/12 00:45, Scott Aron Bloom wrote:
>> Nope. That was not the issue. The issue was that when you append
>> list A into list B, you can't get to list A because what's inside list
>
>> B is a copy of A, not A itself. You might want to read again
On 27/04/12 00:45, Scott Aron Bloom wrote:
> Nope. That was not the issue. The issue was that when you append
> list A into list B, you can't get to list A because what's inside list
> B is a copy of A, not A itself. You might want to read again from the
> first post.
>
>
On 27/04/12 00:45, Scott Aron Bloom wrote:
> Nope. That was not the issue. The issue was that when you append list
> A into list B, you can't get to list A because what's inside list B is a
> copy of A, not A itself. You might want to read again from the first
> post.
>
> ___
From: interest-bounces+scott.bloom=onshorecs@qt-project.org
[mailto:interest-bounces+scott.bloom=onshorecs@qt-project.org] On
Behalf Of Scott Aron Bloom
Sent: Thursday, April 26, 2012 2:46 PM
To: Nikos Chantziaras; interest@qt-project.org
Subject: Re: [Interest] Help, please !!!
Nope. Tha
Nope. That was not the issue. The issue was that when you append list
A into list B, you can't get to list A because what's inside list B is a
copy of A, not A itself. You might want to read again from the first
post.
___
Nope.. not at all..
On 26/04/12 23:51, Andre Somers wrote:
> Op 26-4-2012 18:47, Nikos Chantziaras schreef:
>> On 26/04/12 19:01, André Somers wrote:
>>> Op 23-4-2012 20:44, Nikos Chantziaras schreef:
Then you're not doing what you think you're doing:
QListlistOfLists;
On Thu, Apr 26, 2012 at 10:51 PM, Andre Somers wrote:
> The copy is made at the moment you _append_ the list, not at the moment
> you're modifying it.
actually, it's made at both points. operator[] (the non-const version)
detaches (which causes a copy, if the container's data is shared).
append a
Op 26-4-2012 18:47, Nikos Chantziaras schreef:
> On 26/04/12 19:01, André Somers wrote:
>> Op 23-4-2012 20:44, Nikos Chantziaras schreef:
>>> Then you're not doing what you think you're doing:
>>>
>>>QList< QList > listOfLists;
>>>QList listOfInts;
>>>listOfInts.appe
Hi all,
I'm struggling with a problem concerning packaging of an Qt-application on Mac
OS X. The program compiles and runs well. Everything works just fine, until
the macdeployqt-tool is invoked. After that the QML-based part of the
application (mainly the startscreen with some funny animations
Hi Alex Blasche and Qt5 Interest list
I tried to compile my application with Qt5 and the QtLocation module and it
failed by the absence of the classes:
QGeoMapPixmapObject
QGeoMapPolylineObject
Are these classes not going to make into QtLocation final?
Could you give me some information of why
On 26/04/12 19:01, André Somers wrote:
> Op 23-4-2012 20:44, Nikos Chantziaras schreef:
>> Then you're not doing what you think you're doing:
>>
>> QList< QList > listOfLists;
>> QList listOfInts;
>> listOfInts.append(10);
>>
>> listOfLists.append(listOfInts);
>> l
Op 24-4-2012 17:01, Andre Haupt schreef:
> On Tue, Apr 24, 2012 at 01:58:00PM +0200, Sujan Dasmahapatra wrote:
>>
>>
>> I have my mainwindow which is QMainWindow the parent of all my other
>> classes. I am type casting upwards from 5 levels down using
>> reinterpret_cast, to access the mainwindow t
Op 23-4-2012 20:44, Nikos Chantziaras schreef:
Then you're not doing what you think you're doing:
QList< QList > listOfLists;
QList listOfInts;
listOfInts.append(10);
listOfLists.append(listOfInts);
listOfLists[0][0] = 9;
qDebug()<< listOfLists[0][0]<<
Determine what the command line should really be.
moc.exe -I"..." -I"Qt\include" -FoRelease @**.moc
I have no idea what is.
What does @** evaluate to?
From: rcyboom
To: Konstantin Tokarev
Cc: "interest@qt-project.org"
Sent: Thursday, April 26, 20
Yes,I know that mingw32-make can do it success.
But I want to know why the Nmake has error?
I has tried use qmake to createing a vs project,but it's failed.
eg:
qmake -tp vc
or
qmake -tp vc -r
How I can solving it?Because on windows,the VS Compiler is faster than mingw.
And In my laptop computer(W
Hi!,
if you are already using a QAbstractTableModel subclass why are you not
using
Qt::TooltipRole in headerData method of your model?
http://qt-project.org/doc/qt-4.8/qabstractitemmodel.html#headerData
Regards,
Miguel Angel.
El 26/04/12 15:53, Carl Schumann escribió:
> Qt community,
>
Qt community,
David, thanks that definitely seems to be heading in a promising direction.
It does create a challenge though. The model that I am using for my
QTableView inherits from QAbstractTableModel. Your proposal appears to
require that I change my model to instead inherit from
QStan
Op 23-4-2012 15:45, lucas.betsch...@crypto.ch schreef:
Quoted from digia.com (digia.com/en/Qt/Digia-is-Committed-to-Qt/):
"
Digia is comitted to:
...
- Advancing the cross-platform Qt promise by supporting leading ( !!
) desktop and embedded platforms
...
"
So we doubtless can expect an offici
On 04/25/2012 04:17 PM, Jason H wrote:
I had considered that, but rejected it because Apple designs and
manufactures its own chips. Therefore, they would change their CPU
design rather than switch architectures.
AFAIK Apple doesn't manufacture their chips - they are in fact, fairly
famous f
26.04.2012, 14:58, "rcyboom" :
> Hi,
> I have a very troubled problem:
> In my Qt Creator,The Nmake sometimes would reported error “U 1038” when I
> building a project.
> It occurs using moc.exe create the *.moc files.
> The Qt Creator's complie output window like:
> ~~~
> ~~~
> moc.exe -I"...
Hi,
I have a very troubled problem:
In my Qt Creator,The Nmake sometimes would reported error “U 1038” when I
building a project.
It occurs using moc.exe create the *.moc files.
The Qt Creator's complie output window like:
~~~
~~~
moc.exe -I"..." -I"Qt\include" -FoRelease @**.moc
nmake retur
> The solution is simple: nothing is required.
>
> If the constructor throws, the language calls operator
> delete. There's no leak. You can confirm by inspecting the assembly
> of the following program:
>
> struct Foo { Foo(); }; Foo *f() { return new Foo; }
>
> You'll notice that the body of the
On quinta-feira, 26 de abril de 2012 10.23.45, Stephen Bryant wrote:
> Hi,
>
> > N, throwing from a constructor is fine. Throwing from a destructor
> > is a big no no. Actually there is no other way to cleanly 'get out'
> > when construction fails.
>
> Ooohh... big disagreement coming up here!
> Consider this line:
>
>Foo *foo = new Foo();
>
> Assuming 'new' succeeds and allocates memory on the heap: if the
> constructor throws, the pointer 'foo' never gets initialised.
> How do you cleanly 'get out' of that one? I.e. how do you delete
> the allocated memory without knowing where i
Hi,
> N, throwing from a constructor is fine. Throwing from a destructor
> is a big no no. Actually there is no other way to cleanly 'get out'
> when construction fails.
Ooohh... big disagreement coming up here!!
Consider this line:
Foo *foo = new Foo();
Assuming 'new' succeeds and all
> -Original Message-
> From: interest-bounces+kai.koehne=nokia@qt-project.org
> [mailto:interest-bounces+kai.koehne=nokia@qt-project.org] On Behalf
> Of ext Sergey
> Sent: Thursday, April 26, 2012 8:25 AM
> To: interest@qt-project.org
> Subject: [Interest] qInstallMsgHandler in QAx
31 matches
Mail list logo
