Re: [Interest] emulate windows 10 behaviour on a QT window

2015-11-10 Thread Andrew Knight
Hi Nicolas, The simple answer is to use Qt for Windows Runtime. Then you get the Windows 10 top bar behavior for free. Of course, that means you won't have access to certain APIs which you would have on Classic Windows Desktop, but maybe that won't be an issue for you. I would suggest starti

Re: [Interest] emulate windows 10 behaviour on a QT window

2015-11-10 Thread Nicolas Jäger
hi, Constantin Makshin wrote : > I don't think you can do much more than maximizing your window when its > Y coordinate becomes less than a certain [small] value. I thought about what you said, there is some problem/limitation with that, because windows 10 does some visual effects. It doesn't

Re: [Interest] emulate windows 10 behaviour on a QT window

2015-11-10 Thread Constantin Makshin
I don't think you can do much more than maximizing your window when its Y coordinate becomes less than a certain [small] value. On 11/11/2015 12:57 AM, Nicolas Jäger wrote: > Hi, > I have to use QT5 on windows 10 (both are not my choice...), I wrote an ui > with QT, I have a > borderless window a

[Interest] emulate windows 10 behaviour on a QT window

2015-11-10 Thread Nicolas Jäger
Hi, I have to use QT5 on windows 10 (both are not my choice...), I wrote an ui with QT, I have a borderless window and I use a widget to make the window bar. I can move the window around the screen by clicking and holding the mouse button on that widget. Now, somebody asks me to emulate the same

[Interest] QML popup window closing

2015-11-10 Thread Juhani Matilainen
Hello, I posted the same question to forum but no answers. I hope you can help. I have modal dialog (qml window) that includes popup window. Popup is closed ok when mouse is clicked outside of popup in modal window. But I'd like to close popup also when is clicked anywhere on screen but outsid

[Interest] QSettings strange behaviour when initialised with organisation and application

2015-11-10 Thread Nuno Santos
Hi, Today I have found the reason behind a strange bug I was having on my settings class, based on QSettings. I have recently moved to a QSettings initialisation with organisation and application parameters. What I have realised is that using this parameters, QSettings doesn’t seem to allow

Re: [Interest] Can QObject::tr() be used in initialization of static const QString data members? [Qt 5.5.1, Windows]

2015-11-10 Thread Matthew Woehlke
On 2015-11-10 13:00, Thiago Macieira wrote: > On Tuesday 10 November 2015 11:31:57 Matthew Woehlke wrote: >> On 2015-11-09 17:35, Thiago Macieira wrote: >>> I advise against static QStrings altogether. Just don't do that. >> >> What's the problem with static QString? > > There's no actual error or

Re: [Interest] Can QObject::tr() be used in initialization of static const QString data members? [Qt 5.5.1, Windows]

2015-11-10 Thread Thiago Macieira
On Tuesday 10 November 2015 11:31:57 Matthew Woehlke wrote: > On 2015-11-09 17:35, Thiago Macieira wrote: > > I advise against static QStrings altogether. Just don't do that. > > What's the problem with static QString? There's no actual error or problem, but it's just poor coding practice. It's

Re: [Interest] Can QObject::tr() be used in initialization of static const QString data members? [Qt 5.5.1, Windows]

2015-11-10 Thread Matthew Woehlke
On 2015-11-09 17:35, Thiago Macieira wrote: > I advise against static QStrings altogether. Just don't do that. What's the problem with static QString? -- Matthew ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/lis

Re: [Interest] Qt at iOS: Crash on null QWindow pointer in QIOSInputContext::scrollToCursor

2015-11-10 Thread Robert Iakobashvili
In general, it's reasonable to let an app decide how to form the Edit Menu and what to include. If doing a native development to the best of my knowledge, you can get rid from standard menu items: https://developer.apple.com/library/ios/documentation/StringsTextFonts/Conceptual/TextAndWebiPhoneOS

Re: [Interest] Qt at iOS: Crash on null QWindow pointer in QIOSInputContext::scrollToCursor

2015-11-10 Thread Gustavsen Richard
Currently the logic is so that if the current focus object in Qt supports text input (Qt::ImEnabled), then the platform plugin will inform iOS that cut/copy/paste actions are supported. iOS will then add extra items in the edit menu, extra buttons on the virtual keyboard (unless you apply your

Re: [Interest] Qt at iOS: Crash on null QWindow pointer in QIOSInputContext::scrollToCursor

2015-11-10 Thread Robert Iakobashvili
Dear Richard, To get rid from Keyboard Shotcuts Bar with Cut/Copy/Paste is rather easy, I'm using the below that works in 4.2 as well as in 5.5.1: 1. Disable predictive input in the window/text-field; 2. Pass the view/window/text-field as Wid (widget->winId()) to the function below and disable two

Re: [Interest] Qt at iOS: Crash on null QWindow pointer in QIOSInputContext::scrollToCursor

2015-11-10 Thread Gustavsen Richard
Hi! If it's the cut/copy/paste actions you mean, it's problematic to remove them fully, since we don't really know if the application needs them or not. If we did, then support for e.g cmd-c on a bluetooth keyboard (or copy button on the virtual keyboard), would be removed as well. But after h

Re: [Interest] Qt at iOS: Crash on null QWindow pointer in QIOSInputContext::scrollToCursor

2015-11-10 Thread Robert Iakobashvili
Hi Richard, I was using 5.4.2, and I see that it was fixed for 5.5 Unfortunately, in Qt-5.5 QPlatformMenu adds Apple's standard MenuItems prior to my custom item, so I cannot make my custom Editing Menu without Apple's standard; this is the reason to continue with 5.4 Can we get rid from Apple'

Re: [Interest] Qt at iOS: Crash on null QWindow pointer in QIOSInputContext::scrollToCursor

2015-11-10 Thread Gustavsen Richard
Which version on Qt are you using? It looks like this was fixed in 5.5: https://codereview.qt-project.org/#/c/109592/ -Richard Fra: Interest på vegne av Robert Iakobashvili Sendt: 10. november 2015 06:49 Til: interest@qt-project.org Emne: [Interest] Qt at iO