On Sat, May 14, 2016 at 01:16:41AM -0400, Scott Kostyshak wrote:
> Hi,
>
> Behavior has changed between 5.5.1 and 5.6.0 and I would like to
> confirm that it is indeed a bug, and also ask if anyone knows a
> workaround?
>
> The bug is posted here:
> https://bugreports.qt.io/browse/QTBUG-53272
>
On terça-feira, 17 de maio de 2016 11:41:59 PDT Hamish Moffatt wrote:
> It seems that for a metatype that is a QList I must
> call qRegisterMetaType with the name specified, else reading properties
> complains that the metatype isn't registered. What worries me is that
> the type name must be speci
> -Original Message-
> From: Interest [mailto:interest-bounces+alexander.blasche=qt.io@qt-
> project.org] On Behalf Of Elvis Stansvik
> 2016-05-15 23:49 GMT+02:00 Thiago Macieira :
> > On domingo, 15 de maio de 2016 10:35:02 PDT Elvis Stansvik wrote:
> >> Hi all,
> >>
> >> Anyone know wh
2016-05-16 22:43 GMT+02:00 Thiago Macieira :
> On segunda-feira, 16 de maio de 2016 18:19:37 PDT Elvis Stansvik wrote:
>> Den 11 maj 2016 7:50 fm skrev "Elvis Stansvik" :
>> > Hi all,
>> >
>> > Setting a QML engine root context property to a QObject instance that
>> > has been moved to a different
On 17 May 2016 at 08:47, Hamish Moffatt wrote:
>
> And do I need to call Q_DECLARE_METATYPE(QList) or
> not? It doesn't seem to be necessary in my test cases
I don't think so. The documentation for Q_DECLARE_METATYPE says that
if Type is registered then QList is automatically recognized by
the met
On 17/05/16 12:02, Larry Martell wrote:
On Mon, May 16, 2016 at 7:53 PM, Hamish Moffatt
wrote:
On 17/05/16 08:24, Larry Martell wrote:
I've see a lot of code that does something like this:
QJsonDocument document = QJsonDocument::fromJson(jsonData);
QJsonObject object = document.ob
On Mon, May 16, 2016 at 7:53 PM, Hamish Moffatt
wrote:
> On 17/05/16 08:24, Larry Martell wrote:
>>
>> I've see a lot of code that does something like this:
>>
>> QJsonDocument document = QJsonDocument::fromJson(jsonData);
>> QJsonObject object = document.object();
>> QJsonValue val
On 17/05/16 11:04, Thiago Macieira wrote:
On terça-feira, 17 de maio de 2016 09:47:18 PDT Hamish Moffatt wrote:
And do I need to call
Q_DECLARE_METATYPE(QList) or not? It doesn't
seem to be necessary in my test cases.
Note that it's a macro declaring a template specialisation, so it's not a
cal
On terça-feira, 17 de maio de 2016 09:47:18 PDT Hamish Moffatt wrote:
> On 17/05/16 01:27, Thiago Macieira wrote:
> > The overhead is almost null because the inline parts of qRegisterMetaType
> > function check whether it's already registered before calling the
> > non-inline parts.
>
> How about
On 17/05/16 08:24, Larry Martell wrote:
I've see a lot of code that does something like this:
QJsonDocument document = QJsonDocument::fromJson(jsonData);
QJsonObject object = document.object();
QJsonValue value = object.value("capData");
But I don't want to hard code the keys - I
On 17/05/16 01:27, Thiago Macieira wrote:
On segunda-feira, 16 de maio de 2016 13:28:09 PDT Nye wrote:
Should I just do it from the constructor?
That would be what I usually do. Still there's overhead of repeatedly
registering the same type, so if you have a better place on hand (a root
object/
I am reading in a JSON file that looks like this:
{
"capData": {
"host": "foo.bar.com",
"initial_port": "8000"
"secondary_port": "8001"
},
"django": {
"host": "baz.bar.com",
"port": "8004"
}
}
I want to iterate through it and put the data in some structur
Hello,
When I start my app on the device, then it seems that the screen is scaled,
because the wireless icon, battery and time are bigger then before. After I
close my app, those icons has there normal size.
How can I manage to disable those scaling?
Regards
___
I managed it to make it work with CMake
> Am 13.05.2016 um 17:13 schrieb NoRulez :
>
> Hello,
>
> I get the following error:
> "Error: You are creating QApplication before calling UIApplicationMain. If
> you are writing a native iOS application, and only want to use Qt for parts
> of the appli
On segunda-feira, 16 de maio de 2016 18:19:37 PDT Elvis Stansvik wrote:
> Den 11 maj 2016 7:50 fm skrev "Elvis Stansvik" :
> > Hi all,
> >
> > Setting a QML engine root context property to a QObject instance that
> > has been moved to a different thread and then attempting to connect to
> >
> > o
I moved my translations to localize.biz because it was recomended by a few
people here. However, this is quickly falling apart over plurals.
Can someone explain to me how plurals map between Qt and Localize? They
recently added the plurality on export, but it's not there for imports so I
have
> -Ursprüngliche Nachricht-
> Von: Interest [mailto:interest-bounces+kai.koehne=qt...@qt-project.org]
> Im Auftrag von Adam Light
> Gesendet: Montag, 16. Mai 2016 20:09
> An: Interest@qt-project.org
> Betreff: [Interest] Qt 5.6.0 online installer does not provide VS runtime
> libraries
>
>
On a Windows 10 virtual machine that is essentially a clean install of
Windows 10, I went to http://www.qt.io/download-open-source/ and downloaded
the online installer (
http://download.qt.io/official_releases/online_installers/qt-unified-windows-x86-online.exe).
I then executed the application and
Den 11 maj 2016 7:50 fm skrev "Elvis Stansvik" :
>
> Hi all,
>
> Setting a QML engine root context property to a QObject instance that
> has been moved to a different thread and then attempting to connect to
> one of its signals with Connections on the QML side seems unsupported:
>
> QQmlEngin
On segunda-feira, 16 de maio de 2016 13:28:09 PDT Nye wrote:
> > Should I just do it from the constructor?
>
> That would be what I usually do. Still there's overhead of repeatedly
> registering the same type, so if you have a better place on hand (a root
> object/entry point of your application/l
I used Qt 5.6 (commercial edition) QMediaPlayer to play a simple local mp3 file
on iPhone5 and iPhone 6, both running ios 8.4.
On iphone 5 , audio output to the loudspeacker. But on iPhone 6 , audio output
to the jack and I need to use a headset to listen audio output.
Then I use an iPhone 6s Pl
>
> Should I just do it from the constructor?
That would be what I usually do. Still there's overhead of repeatedly
registering the same type, so if you have a better place on hand (a root
object/entry point of your application/library) that'd be better.
> Would I need to worry about thread saf
22 matches
Mail list logo
