[Development] Bluetooth Services problem

2016-05-04 Thread Matías Néstor Ares
Hi Everybody!! I'm having an issue with bluetooth on QML on android Qt 5.6.0 I can't even fully test the example: http://doc.qt.io/qt-5/qtbluetooth-scanner-example.html trying to access service inside onServiceDiscovered: it gets undefined. as documentation says : *serviceDiscovered(Bluetooth

Re: [Development] Documentation for QPagedPrintDevice::setPageSize should specify a unit`

2016-05-04 Thread Steve Schilz
Oops, I ment QTextDocument::setPageSize (http://doc.qt.io/qt-5/qtextdocument.html#pageSize-prop) Does that make more sense? Steve Schilz PASCO scientific - think science On 5/4/16, 2:17 PM, "Giuseppe D'Angelo" wrote: >Hi, > >On Wed, May 4, 2016 at 10:09 PM, Steve Schilz wrote: >> The

Re: [Development] Documentation for QPagedPrintDevice::setPageSize should specify a unit

2016-05-04 Thread Giuseppe D'Angelo
Hi, On Wed, May 4, 2016 at 10:09 PM, Steve Schilz wrote: > The doc is confusing because it does not specify a unit for the input > parameter “pageSize" The parameter is of type QPageSize, which has multiple setters and constructors. Which one(s) is missing the unit specification? Thanks, -- Gi

[Development] Documentation for QPagedPrintDevice::setPageSize should specify a unit

2016-05-04 Thread Steve Schilz
Hi, I would like to suggest a small update to the documentation for QPagedPaintDevice::setPageSize(const QPageSize &pageSize) See https://doc-snapshots.qt.io/qt5-5.7/qpagedpaintdevice.html#setPageSize i The doc is confusing because it does not specify a unit for the input parameter “pageSize"

Re: [Development] -developer-build (was: [5.7-beta] compile error with xcode-6.4

2016-05-04 Thread Thiago Macieira
On quarta-feira, 4 de maio de 2016 17:10:30 PDT Mark De Wit wrote: > Hmm, is that proving my point, though? My understanding was that compiling > Qt in a namespace and with unique filename was recommended to avoid > (minimise) the likelihood of conflicting Qt versions in a single process. That is

Re: [Development] -developer-build (was: [5.7-beta] compile error with xcode-6.4

2016-05-04 Thread Mark De Wit
Hmm, is that proving my point, though? My understanding was that compiling Qt in a namespace and with unique filename was recommended to avoid (minimise) the likelihood of conflicting Qt versions in a single process. Is there documentation that states how one should build Qt for release with t

Re: [Development] -developer-build (was: [5.7-beta] compile error with xcode-6.4

2016-05-04 Thread Thiago Macieira
On quarta-feira, 4 de maio de 2016 07:46:41 PDT Mark De Wit wrote: > The configure flags are poorly documented, and options like qtlibinfix > (which I understood to be a recommended best practice) isn't even mentioned > on the configure flag page. Because it isn't a recommended best practice. --

Re: [Development] [5.7-beta] compile error with xcode-6.4

2016-05-04 Thread Tim Blechmann
>> * legacy code using deprecated sdk functions might not compile a certain >> codebase (depending on the age of your codebase this maybe lead to >> significant effort) > > Is that because of bugs you talked about below, or is there another reason > why > this would happen? Why would it not comp

Re: [Development] Scope of source code license files

2016-05-04 Thread Lars Knoll
On 02/05/16 14:37, "Development on behalf of Sze Howe Koh" wrote: >Hello, > >The LICENSE.GPLvX and LICENSE.LGPLvX files from >http://code.qt.io/cgit/qt/qtbase.git/tree/ (and submodules) start with >"The Qt Toolkit is Copyright (C) 2015...", but then they go on to say >"You may use, distribute

Re: [Development] -developer-build (was: [5.7-beta] compile error with xcode-6.4

2016-05-04 Thread Mark De Wit
Having tried to do this myself last week, I cannot find any "official" documentation on how to build Qt myself for an official release with our software. Doing our own build has proven frustrating enough that we abandoned the current attempt to update our version of Qt. The configure flags are

Re: [Development] [5.7-beta] compile error with xcode-6.4

2016-05-04 Thread Thiago Macieira
On quarta-feira, 4 de maio de 2016 07:55:21 PDT Tim Blechmann wrote: > * legacy code using deprecated sdk functions might not compile a certain > codebase (depending on the age of your codebase this maybe lead to > significant effort) Is that because of bugs you talked about below, or is there ano