Re: [Development] Are QT winmigrate framework will be back in qt 5.x ?

Thinks for reply, nice of you. I have an application that based on MFC MDI and it call 300+ DLLs(based on MFC, type is MFC regular DLL, each DLL contains GUI based on Dialog, and each DLL send && receive messages with MFC MDI application, as a plugin cowork with the MFC MDI application). for some

Re: [Development] Programs crashing left and right in the CI

Excellent summary. I'd like to add one point: The crashes appear to happen with a big majority in qtbase. Outside of qtbase I've only seen moc crash, on macOS I think. Simon From: Development on

[Development] [QLockFile] Whether it is reasonable to use 0644 permission ?

Hi all. As I can see, the QLockFile opens a lock-file with the 0644 permissions in Linux, e.g. see QLockFile::LockError QLockFilePrivate::tryLock_sys() [1]. That means that only one user (owner) can modify this file. But it leads to problems, for example, when this use-case: 1. User 'A'

Re: [Development] Programs crashing left and right in the CI

On Wednesday 27 of July 2016 08:28:08 Friedemann Kleint wrote: > Hi, > > to summarize for Windows: > > - Crashes have been observed over time in various tests, mostly in > QtCore (QDir,QFile, QProcess see fex > https://bugreports.qt.io/browse/QTBUG-47370 > > - It only affects 64bit (!) (correct

Re: [Development] QML: Why C++11 scoped enums are not scoped in QML?

On miercuri, 27 iulie 2016 10:35:01 EEST André Somers wrote: > Op 27/07/2016 om 09:53 schreef BogDan Vatra: > >> That said, it would be a behavior change not to allow anymore the > >> previous > >> (unscoped) syntax to work with QML > > > > The unscoped enums should work as they are woring now,

Re: [Development] [QLockFile] Whether it is reasonable to use 0644 permission ?

On quarta-feira, 27 de julho de 2016 09:49:14 PDT Denis Shienkov wrote: > Why just do not use 0666 permissions for this? We should use 0666 and let the umask determine which bits to exclude. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology

Re: [Development] Programs crashing left and right in the CI

On Tuesday 26 of July 2016 15:30:48 Thiago Macieira wrote: > Em terça-feira, 26 de julho de 2016, às 23:24:21 PDT, Giuseppe D'Angelo > > escreveu: > > On Mon, Jul 25, 2016 at 5:51 PM, Thiago Macieira > > > > wrote: > > > Let's pay attention of what crashes and where.

Re: [Development] QML: Why C++11 scoped enums are not scoped in QML?

On marți, 26 iulie 2016 20:08:52 EEST Olivier Goffart wrote: > On Dienstag, 26. Juli 2016 08:33:31 CEST Thiago Macieira wrote: > > Em terça-feira, 26 de julho de 2016, às 17:50:38 PDT, BogDan Vatra escreveu: > > > Hi, > > > > > > Is there any reason why C++11 scoped enums are not scoped in QML ?

Re: [Development] QML: Why C++11 scoped enums are not scoped in QML?

Op 27/07/2016 om 09:53 schreef BogDan Vatra: That said, it would be a behavior change not to allow anymore the previous (unscoped) syntax to work with QML The unscoped enums should work as they are woring now, just the scoped ones should be scoped in QML as well. Based on your patch, I'll

Re: [Development] QML: Why C++11 scoped enums are not scoped in QML?

On Wed, Jul 27, 2016 at 10:47 AM, BogDan Vatra wrote: > Of course if we can find a better solution to have them both is even better ! I guess you'll need a pragma to enable this feature as opt-in. And/or a pragma to warn about the other usage so that in 5.10/5.11 you can break

Re: [Development] Programs crashing left and right in the CI

Hi, to summarize for Windows: - Crashes have been observed over time in various tests, mostly in QtCore (QDir,QFile, QProcess see fex https://bugreports.qt.io/browse/QTBUG-47370 - It only affects 64bit (!) (correct me if you have observed otherwise) - It never has been observed for MinGW

Re: [Development] [QLockFile] Whether it is reasonable to use 0644 permission ?

> and let the umask determine which bits to exclude. what do you mean here? why we need to use umask, and why we need to exclude bits? 27.07.2016 10:01, Thiago Macieira пишет: On quarta-feira, 27 de julho de 2016 09:49:14 PDT Denis Shienkov wrote: Why just do not use 0666 permissions for

Re: [Development] [QLockFile] Whether it is reasonable to use 0644 permission ?

FWIW this is slightly related to https://bugreports.qt.io/browse/QTBUG-53570 On Wed, Jul 27, 2016 at 9:31 AM, Denis Shienkov wrote: >> and let the umask determine which bits to exclude. > > what do you mean here? why we need to use umask, and why we need to exclude >

[Development] Fwd: Are there any limitations on implementing the changing of the screen for a QWindow on systems using EGLFS?

I've seen that patch, and it is definitely a good starter. I was able to change the screen and run two screens simultaneously using Raspbian's Dispmanx example (one screen was connected through the PI's DSI port the other one through HDMI) quite easily, so I think it does worth poking around with.

Re: [Development] [QLockFile] Whether it is reasonable to use 0644 permission ?

On Wed, Jul 27, 2016 at 12:01:20AM -0700, Thiago Macieira wrote: > On quarta-feira, 27 de julho de 2016 09:49:14 PDT Denis Shienkov wrote: > > Why just do not use 0666 permissions for this? > > We should use 0666 and let the umask determine which bits to exclude. > how exactly is this response

Re: [Development] [QLockFile] Whether it is reasonable to use 0644 permission ?

On Wed, Jul 27, 2016 at 09:49:14AM +0300, Denis Shienkov wrote: > Currently this problem belongs to QSerialPort which internally uses > QLockFile to indication of employment of the /dev/ttyXYZ resources. > well, that's kinda the problem. this approach is a hack to work around inadequate locking

Re: [Development] [QLockFile] Whether it is reasonable to use 0644 permission ?

On quarta-feira, 27 de julho de 2016 11:37:51 PDT Oswald Buddenhagen wrote: > also, isn't this actually mostly about the permissions of the directory > containing the locks? lock grabbing should be mostly about deleting and > re-creating the file. That's also a good point. If you have permission

Re: [Development] Is the MNG format supported in official installer?

On quarta-feira, 27 de julho de 2016 15:06:29 PDT Denis Shienkov wrote: > Ahh... seems, the config.tests for MNG fails.. That's because we removed the bundled copy of libmng. You need to install it yourself first. We did that because our copy was very old and, at Qt 5.6 times, we thought that

Re: [Development] Programs crashing left and right in the CI

On quarta-feira, 27 de julho de 2016 09:53:32 PDT Jędrzej Nowacki wrote: > No, the machine gets destroyed after test failure. Normally gdb session is > attached to crashing process, that was not the case for some odd reason. > Can it be that QTestLib is crashing too? There have been tools to

Re: [Development] QML: Why C++11 scoped enums are not scoped in QML?

On quarta-feira, 27 de julho de 2016 11:47:03 PDT BogDan Vatra wrote: > On miercuri, 27 iulie 2016 10:35:01 EEST André Somers wrote: > > Op 27/07/2016 om 09:53 schreef BogDan Vatra: > > Would that not break existing QML applications that now use enums backed > > by scoped enums in C++? > > It

Re: [Development] [QLockFile] Whether it is reasonable to use 0644 permission ?

Thiago Macieira wrote: > If you don't have permission to delete it, then you're going to have a > problem to drop your own lock if you steal the lock by writing to the > file. So this means that the permission should be 0644 to prevent that from happening. Thus, I don't understand how you get

Re: [Development] Programs crashing left and right in the CI

On Tue, Jul 26, 2016 at 11:24 PM, Giuseppe D'Angelo wrote: > > > It just happened again: > >

Re: [Development] [QLockFile] Whether it is reasonable to use 0644 permission ?

On quarta-feira, 27 de julho de 2016 22:15:45 PDT Kevin Kofler wrote: > Thiago Macieira wrote: > > If you don't have permission to delete it, then you're going to have a > > problem to drop your own lock if you steal the lock by writing to the > > file. > > So this means that the permission

Re: [Development] Programs crashing left and right in the CI

On Wed, Jul 27, 2016 at 11:00 PM, Giuseppe D'Angelo wrote: > >>

Re: [Development] [QLockFile] Whether it is reasonable to use 0644 permission ?

On quarta-feira, 27 de julho de 2016 10:31:35 PDT Denis Shienkov wrote: > > and let the umask determine which bits to exclude. > > what do you mean here? why we need to use umask, and why we need to > exclude bits? Because we don't have a choice. The umask bits apply when you create a fie. --

Re: [Development] Programs crashing left and right in the CI

On quarta-feira, 27 de julho de 2016 23:00:36 PDT Giuseppe D'Angelo wrote: > On Tue, Jul 26, 2016 at 11:24 PM, Giuseppe D'Angelo wrote: > > It just happened again: > > > > http://testresults.qt.io/logs/qt/qtbase/ddfe2ba984be5d652fe500f6695040959d > >

[Development] New Coin feature: automatic provisioning

Hi, Good news everyone! Last month we managed to deploy a new automatic provisioning system to Coin. What does it mean to you? Now you can modify existing VM templates used by Coin. Installing additional packages should be trivial and more or less safe from now. I. The goal: - Coin

Re: [Development] Is the MNG format supported in official installer?

Hmm.. Now I have cloned the "imageformats" source module, open its *.pro file from QtC, and re-build it... BUT: I too do not see the output qmng.dll target, though, I see this 'mng' plugin in the source's tree... Seems it did not compiles.. o_O 2016-07-27 14:47 GMT+03:00 Denis Shienkov

[Development] Is the MNG format supported in official installer?

Hi all. I want to use an MNG animation, using official Qt 5.7 from MSVC2015 installer.. BUT: I do not see in 5.7\msvc2015\plugins\imageformats\ apropriate qmng.dll (or something like) plugin, so leads to fails with the QML's AnimatedSprite item, with error: : QML Sprite: Error decoding:

Re: [Development] New Coin feature: automatic provisioning

Hi, Am 07/27/2016 um 01:47 PM schrieb Jędrzej Nowacki: > Hi, > > Good news everyone! Last month we managed to deploy a new automatic > provisioning system to Coin. What does it mean to you? Now you can modify > existing VM templates used by Coin. Installing additional packages should be >

Re: [Development] Is the MNG format supported in official installer?

Ahh... seems, the config.tests for MNG fails.. 2016-07-27 15:03 GMT+03:00 Denis Shienkov : > Hmm.. Now I have cloned the "imageformats" source module, open its *.pro > file from QtC, and re-build it... > > BUT: I too do not see the output qmng.dll target, though, I see

Re: [Development] New Coin feature: automatic provisioning

On Wednesday 27 of July 2016 13:58:44 Dominik Holland wrote: > Hi, > > Am 07/27/2016 um 01:47 PM schrieb Jędrzej Nowacki: > > Hi, > > > > Good news everyone! Last month we managed to deploy a new automatic > > > > provisioning system to Coin. What does it mean to you? Now you can modify > >