Re: [Development] QtSingleApplication in Qt proper?

On terça-feira, 21 de junho de 2016 01:17:07 PDT André Pönitz wrote: > > I'd like to see KUniqueApplication deprecated, as it relies on some > > undocumented and fragile QtDBus functionality (namely, connecting to > > the bus before QCoreApplication is created). > > That's a reason that I have

Re: [Development] QtSingleApplication in Qt proper?

On Mon, Jun 20, 2016 at 02:16:37PM -0700, Thiago Macieira wrote: > > You mean port away from QApplication? > > > > Anyway, I don't quite get it: > > > > - QtSingleApplication is as easily accessible as other "bread and > > butter" parts of Qt via git, hosted by the same entity, > > > > - no

Re: [Development] Qt 5.7.0 Toolchain on RasPI2

On segunda-feira, 20 de junho de 2016 21:30:09 PDT Alexander Nassian wrote: > Hi Thiago, > > Would be great if you could be a little bit more specific. I’m using exactly > the same toolchain and the same sysroot for 5.5.1 and 5.7.0. The 5.5.1 > build works perfectly, the 5.7.0 build fails while

Re: [Development] QtSingleApplication in Qt proper?

On segunda-feira, 20 de junho de 2016 22:57:38 PDT André Pönitz wrote: > On Mon, Jun 20, 2016 at 07:59:32AM +0200, Kevin Funk wrote: > > On Donnerstag, 16. Juni 2016 00:19:10 CEST Kevin Funk wrote: > > > (snip) > > > > > > Question: Is there an interest in having QtSingleApplication in Qt > > >

Re: [Development] QtSingleApplication in Qt proper?

On Mon, Jun 20, 2016 at 07:59:32AM +0200, Kevin Funk wrote: > On Donnerstag, 16. Juni 2016 00:19:10 CEST Kevin Funk wrote: > > (snip) > > > > Question: Is there an interest in having QtSingleApplication in Qt > > proper? Say qtbase? We'd love to do the work if there's a chance for > > it being

Re: [Development] Qt 5.7.0 Toolchain on RasPI2

Hi Thiago, Would be great if you could be a little bit more specific. I’m using exactly the same toolchain and the same sysroot for 5.5.1 and 5.7.0. The 5.5.1 build works perfectly, the 5.7.0 build fails while linking. Is the GCC 4.8.3 which is used for Raspian not supported anymore? Beste

Re: [Development] QtSingleApplication in Qt proper?

+1, I've found many good uses for QtSingleApplication, and think this is a good (highly practical) feature for "Qt-proper". --charley On Sun, Jun 19, 2016 at 11:59 PM, Kevin Funk wrote: > On Donnerstag, 16. Juni 2016 00:19:10 CEST Kevin Funk wrote: > > (snip) > > > > Question:

Re: [Development] Revisiting high-DPI configuration options

On segunda-feira, 20 de junho de 2016 14:30:19 PDT Shawn Rutledge wrote: > Don’t you think there should be a quirks database somewhere (outside of Qt) > which corrects these cases? The TV model can be identified, right? > X does it, but that’s not a broad enough scope to cover Wayland. > >

Re: [Development] QStorageinfo changes: a bug.

On segunda-feira, 20 de junho de 2016 11:45:23 PDT Stef Bon wrote: > This worked until recently, now the fuse is not found anymore. I've > found out that the function > isPseudoFs has been changed, and every fs where the device does not > start with a slash is a pseudofs. Huhhh? This is far too

Re: [Development] Proposal For Qt 5.8 Platforms And SW Updates

Looks good to me. Note that it's macOS now, not OS X. On Jun 20, 2016, at 5:15 AM, Heikki Halmet > wrote: Hi, Below is our proposal for target platforms and sw updates in Qt 5.8 release. Some might come after feature freeze or some changes might

Re: [Development] Revisiting high-DPI configuration options

> On 17 Jun 2016, at 22:49, Thiago Macieira wrote: > >> - Run "./highdpi --metrics", or test with an application. > > See 3 scenarios attached. I'll send a fourth scenario later, when I try at > home with my 45" TV that reports its size as 160 x 90 mm. Don’t you

Re: [Development] Revisiting high-DPI configuration options

> On 17 Jun 2016, at 14:54, Frank Hemer wrote: > > Can you give a hint on what causes these glitches and how to avoid them? > I'm not talking about general usage of fractional methods for painting here. > > For example when drawing to a pixmap (sized for the 'real' screen

Re: [Development] QStorageinfo changes: a bug.

2016-06-20 14:48 GMT+02:00 Shawn Rutledge : > > > Apparently you are referring to https://codereview.qt-project.org/#/c/141217/ > Yes. > Please report a bug, and give any ideas you have for deciding what is a > pseudo-fs and what isn’t. I don’t think we can say that

Re: [Development] QStorageinfo changes: a bug.

> On 20 Jun 2016, at 11:45, Stef Bon wrote: > > Hi, > > I've found aout that the qstorageinfo has changed recently. I'v got a > fuse filesystem and a qt gui using that filesystem. To detect the > mountpoint the gui uses QStorageInfo::mountedVolumes() and walk this > list. >

[Development] Common consensus about isExposed()?

It looks like isExposed() has it's own interpretation of the implementation on each platform. See bug: https://bugreports.qt.io/browse/QTBUG-53252 "isExposed() returns true also if window minimized or completely covered". Our autotests are heavily relying on the result of

[Development] Proposal For Qt 5.8 Platforms And SW Updates

Hi, Below is our proposal for target platforms and sw updates in Qt 5.8 release. Some might come after feature freeze or some changes might not happen at all. OpenSUSE 42.1 x86_64 ( - OpenSUSE 13.1 will be dropped after 42.1 is in) * Openssl: 1.0.2h Rhel 6.6 (build's packages) & Rhel 7.2 x86_64

Re: [Development] Qt 5.8 branching & Feature Freeze

Hi all, It seems there isn't that much objections to proposed schedule. Tony's points are valid but after discussion with several persons we agree it isn't necessary to postpone feature freeze because of missing platforms/versions from CI. So let's proceed with proposed schedule to be able to

Re: [Development] QtSerialBus : Function Code 20 and 21 not implemented

Hi Vincent, we just didn't manage to implement all functionallity provided by the specification. Right now there is no pending patch or implementation I know of, but we are definitifly looking into finishing it for a later release. Of course, if you need the functionality you can implement it

Re: [Development] Qt 5.7.0 Toolchain on RasPI2

On domingo, 19 de junho de 2016 21:36:21 PDT Alexander Nassian wrote: > EGLFS and others were disabled because of the already mentioned linker > error. > > /home/picaschaf/workspace/RATIO-Elektronik_AlignmentTrap/rfs/lib/arm-linux-g > nueabihf/libpthread.so.0: undefined reference to

Re: [Development] QtSingleApplication in Qt proper?

On Donnerstag, 16. Juni 2016 00:19:10 CEST Kevin Funk wrote: > (snip) > > Question: > Is there an interest in having QtSingleApplication in Qt proper? Say > qtbase? We'd love to do the work if there's a chance for it being accepted. Heya, Thanks for all the comments, I'll work on introducing