[Development] Qt 5.11.2 i386 (32-bit) build break fix

2018-09-21 Thread Thiago Macieira
This is mostly for Linux packagers on this mailing list If you're building 32-bit x86 Linux with Qt 5.11.2, you'll likely need this patch: https://codereview.qt-project.org/240702 It's harmless on all other platforms. The error was (so Google search will find this email): error: undefined refe

Re: [Development] 5.12 alpha: Uppercase text input broken on Mac?

2018-09-21 Thread Tor Arne Vestbø
Timur, this should be fixed by your patch right? Tor Arne > On 21 Sep 2018, at 15:36, Nils Jeisecke via Development > wrote: > > Seems that "Shift" acts like "Ctrl+Shift". > > Am 21.09.2018 um 15:22 hat Nils Jeisecke via Development geschrieben: >> not sure if this a mac only problem but I'

Re: [Development] 5.12 alpha: Uppercase text input broken on Mac?

2018-09-21 Thread Nils Jeisecke via Development
Seems that "Shift" acts like "Ctrl+Shift". Am 21.09.2018 um 15:22 hat Nils Jeisecke via Development geschrieben: > not sure if this a mac only problem but I've just noticed that with 5.12 > alpha uppercase letters can no longer be typed in LineEdit etc. > > I can easily reproduce this with the s

[Development] 5.12 alpha: Uppercase text input broken on Mac?

2018-09-21 Thread Nils Jeisecke via Development
Hi, not sure if this a mac only problem but I've just noticed that with 5.12 alpha uppercase letters can no longer be typed in LineEdit etc. I can easily reproduce this with the stock applications like Designer. macOS 10.13.16 Can anybody confirm this? Nils ___

Re: [Development] Closing issues automatically with new keyword

2018-09-21 Thread Kari Oikarinen
On 21.09.2018 15:32, Tor Arne Vestbø wrote: On 21 Sep 2018, at 13:32, Jedrzej Nowacki wrote: Shouldn’t that pick refs/heads/5.11? Tor Arne Yes, that is what happened. The first release branch for 5.11 is 5.11.0, therefore it marked 5.11.0 as fixed version. That doesn’t make any sense.

Re: [Development] Closing issues automatically with new keyword

2018-09-21 Thread Tor Arne Vestbø
> On 21 Sep 2018, at 13:32, Jedrzej Nowacki wrote: >> >> Shouldn’t that pick refs/heads/5.11? >> >> Tor Arne > > Yes, that is what happened. The first release branch for 5.11 is 5.11.0, > therefore it marked 5.11.0 as fixed version. That doesn’t make any sense. The 5.11 branch is constantly

Re: [Development] Closing issues automatically with new keyword

2018-09-21 Thread Jedrzej Nowacki
On Friday, September 21, 2018 1:02:10 PM CEST Tor Arne Vestbø wrote: > > On 21 Sep 2018, at 12:47, Jedrzej Nowacki wrote: > > > > On Friday, September 21, 2018 9:07:14 AM CEST Sami Nurmenniemi wrote: > > > >> I committed this to 5.11 branch: > >> https://codereview.qt-project.org/#/c/240566/ > >

Re: [Development] Closing issues automatically with new keyword

2018-09-21 Thread Tor Arne Vestbø
> On 21 Sep 2018, at 12:47, Jedrzej Nowacki wrote: > > On Friday, September 21, 2018 9:07:14 AM CEST Sami Nurmenniemi wrote: >> I committed this to 5.11 branch: >> https://codereview.qt-project.org/#/c/240566/ >> >> Now Gerrit Bot marked this as fixed in 5.11.0, which is not correct: >> https:

Re: [Development] Closing issues automatically with new keyword

2018-09-21 Thread Sami Nurmenniemi
> I looked into the code... That happened because none of these commands > returned 5.11.x: > git show-ref --tags > git show-ref --heads > So from the bot perspective 5.11 branch was never released therefore 5.11.0 is > the next release. For me it looks quite sane, who can add missing tags? Than

Re: [Development] Closing issues automatically with new keyword

2018-09-21 Thread Jedrzej Nowacki
On Friday, September 21, 2018 9:07:14 AM CEST Sami Nurmenniemi wrote: > I committed this to 5.11 branch: > https://codereview.qt-project.org/#/c/240566/ > > Now Gerrit Bot marked this as fixed in 5.11.0, which is not correct: > https://bugreports.qt.io/browse/QTBUG-70493 > > I'm not sure if it sh

Re: [Development] Best practices for hacking Qt in QtCreator?

2018-09-21 Thread Nils Jeisecke via Development
Hi, Am 21.09.2018 um 09:16 hat Sean Harmer geschrieben: > Works fine here as long as you open the project using a kit set up from that > particular build of Qt. I tend to just build qtbase etc on the command line, > setup a kit in creator for it, then open qt3d/qt3d.pro and it just works. Ok, I've

Re: [Development] Best practices for hacking Qt in QtCreator?

2018-09-21 Thread Sean Harmer
On 21/09/2018 08:41, Nils Jeisecke via Development wrote: Hi there, although I'm usually using vim as my primary environment when hacking Qt itself it can be tempting to use QtCreator instead for better code navigation etc. Simply opening the .pro file of some Qt submodule does not really work

[Development] Best practices for hacking Qt in QtCreator?

2018-09-21 Thread Nils Jeisecke via Development
Hi there, although I'm usually using vim as my primary environment when hacking Qt itself it can be tempting to use QtCreator instead for better code navigation etc. Simply opening the .pro file of some Qt submodule does not really work out of the box. Lots of complaints about Qt includes not fou

Re: [Development] Closing issues automatically with new keyword

2018-09-21 Thread Sami Nurmenniemi
I committed this to 5.11 branch: https://codereview.qt-project.org/#/c/240566/ Now Gerrit Bot marked this as fixed in 5.11.0, which is not correct: https://bugreports.qt.io/browse/QTBUG-70493 I'm not sure if it should automatically select the next unreleased version (5.11.3) or use more general