Re: [Interest] Fwd: Qt 5.7+ and Command+Shift shortcuts on Mac

[René J . V . Bertin]

On Friday January 06 2017 18:33:01 David Faure wrote:

> Well, you didn't say either way, so I tried to guess from your description, 
> and guessed wrong.

No problem, can't be right all the time (and it's Friday night at that) ;)

> > the shortcut shows up correctly (Command-<) but doesn't work.
> 
> ... which brings me back to trying a simple QAction::setShortcut first.

A bunch of observations already, from a simple test thingy I had lying around, 
and reverting temporarily to Qt 5.6.2 :

// QKeySequence(Ctrl+Comma) doesn't work probably because normally owned by the 
system; doesn't show either.

// shows as Shift-Command-, :
// restoreAction->setShortcut(QKeySequence(Qt::CTRL + Qt::SHIFT + 
Qt::Key_Comma));
// shows as Command-< :
// restoreAction->setShortcut(QKeySequence(Qt::CTRL + Qt::Key_Less));
// shows as Shift-Command-1 :
// restoreAction->setShortcut(QKeySequence(Qt::CTRL + Qt::SHIFT + 
Qt::Key_1));
// shows as Command-! :
restoreAction->setShortcut(QKeySequence(Qt::CTRL + Qt::Key_Exclam));

It's probably to expected that Ctrl+Shift+1 is shown as such, and Ctrl+! as 
such too even if Qt could be aware of the kind of keyboard I have configured. 
In this pure Qt code they all work as expected provided I'm not trespassing on 
what is normally a system shortcut like Command+, (open Preferences) which 
doesn't even appear in the menu.

However:
- running the application with the XCB QPA still shows the shortcuts but none 
work. the SwapCtrlAndMeta attribute is unset with the XCB plugin, so shortcuts 
should function as on Linux/X11, and with KF5 applications they do when.

- In KF5 applications I have no problem redefining Command+; it will show in 
the menu, but will continue to perform the system action

- Important: Command+Shift+Letter shortcuts are not concerned, only shortcuts 
that include a "special" symbol which is accessible only under the shift.

- This also applies to Ctrl+Shift+Key shortcuts: Ctrl+! and Ctrl+< are just as 
dead as Command+! and Command+< . In KF5 applications but not in pure Qt.

- Adding some debug print probes in QNSView:keyDown: and QNSView:keyUp: I 
notice the following when defining a keycut with kxmlgui (the standard_actions 
KCM):

* press Ctrl[+Shift]+key, release key: keyDown event followed by keyUp event 
when I release 
* press Command[+Shift]+key, release key: only a keyDown event, no keyUp event.

Does kxmlgui shortcut recorder depend on keyUp/keyRelease events? If so, is 
there a way to monitor them (or where would I add a snooper without having to 
rewrite significant parts of unknown code? I'd add probes in Qt 5.6.2 but no 
longer have the build directory (and rebuilding would take hours).

I did reactivate Qt 5.6.2 and all the 5.29.0 frameworks that I had rebuilt 
against 5.7.1 . All frameworks were thus built against 5.6.2 .

This did NOT restore Command+Shift+Key functionality meaning that this 
particular regression was probably introduced between frameworks 5.27.0 and 
5.29.0 .

What does work with 5.6.2 is Ctrl+Shift+Symbol (tested with Ctrl-< in Kate5). 
Going back to Qt 5.6.2 restored the regression.
I saved that shortcut to the default scheme so I could look at it, for instance:



On Mac/Cocoa this corresponds to main "Ctrl+," and alt. "Command+<" (the 
difference was only to be sure how the comma is stored). The main shortcut 
works, the alternative doesn't.
I tried editing this to "Meta+Shift+,; Ctrl+Shift+,;", but kxmlgui converts 
that to to shortcuts "Ctrl+," and "Command+<" (sic!). The former works as such, 
the latter doesn't.

All in all I'm tempted to say that the regression lies mostly in KF5 and the 
way it interacts with Qt.

For now I'm converting my crucial concerned shortcuts to Ctrl+Command+Key 
because that works ...

R.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Failed first try with Qt on Android

[h...@technosis.de]

Thanks a lot. That fixed it. Don't know what was wrong in the 
".pro.user". I did not even look at it ever before.

Gradle was set before.

So thanks again and have a nice weekend as I will have now ...


Am 06.01.2017 um 13:07 schrieb Petar Koretić:

Try removing .pro.user to reconfigure kits (close project, remove
.pro.user, open .pro)
Switch to gradle if you use ant - Projects > Buld Android APK > Details

Use Gradle

This should reset it enough to give you a clean start


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] C++Now (May-2017) Call For Submissions is open

[charleyb123 .]

http://cppnow.org/2017-conference/announcements/2017/01/06/call-for-submission.html
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How to include a .r header file in a Qt Mac OSX project via qmake?

[Thiago Macieira]

Em sexta-feira, 6 de janeiro de 2017, às 12:09:19 PST, Nuno Santos escreveu:
> Hi,
> 
> I’m working a project based on a Apple example that has a .r file. I don’t
> know exactly what Xcode does with it but I want to manage my project with
> Qt qmake and not with xcode. How can I tell qmake to process the .r file?
> 
> Anyone knows what is this .r file? It seems like a header file but it has .r
> instead of .h

If you #include it only, then no buildsystem cares about it. You don't have to 
do anything.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qmake one-line Qt version checking?

[André Hartmann]

Hi Michael,

Am 06.01.2017 um 13:34 schrieb Michael Sué:

Hi,


#if QT_VERSION < 0x050800
#   error "This program requires Qt 5.8 or higher"
#endif


You can use:
lessThan(QT_VERSION, 5.8.0): message(This program requires Qt 5.8 or higher)


That works indeed - thank you very much!

André


- Michael.


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest



___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qmake one-line Qt version checking?

[Michael Sué]

Hi,

>#if QT_VERSION < 0x050800
>#  error "This program requires Qt 5.8 or higher"
>#endif

You can use: 
lessThan(QT_VERSION, 5.8.0): message(This program requires Qt 5.8 or higher)

- Michael.


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] How to include a .r header file in a Qt Mac OSX project via qmake?

[Nuno Santos]

Hi,

I’m working a project based on a Apple example that has a .r file. I don’t know 
exactly what Xcode does with it but I want to manage my project with Qt qmake 
and not with xcode. How can I tell qmake to process the .r file?

Anyone knows what is this .r file? It seems like a header file but it has .r 
instead of .h 

Thanks!

Regards,

Nuno
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Failed first try with Qt on Android

[Petar Koretić]

Try removing .pro.user to reconfigure kits (close project, remove
.pro.user, open .pro)
Switch to gradle if you use ant - Projects > Buld Android APK > Details >
Use Gradle
This should reset it enough to give you a clean start

On Fri, Jan 6, 2017 at 12:02 PM, h...@technosis.de  wrote:

> Installing the generated apk by hand on the device does work.
> So it seems to be a deploying issue.
>
>
> Am 05.01.2017 um 15:41 schrieb h...@technosis.de:
>
>> Hi,
>>
>> I just started to evaluate Qt on Android and I'm unfortunately stuck in
>> the beginning. Maybe someone has a hint for me.
>>
>> The problem: When running a new Hello World Project or a standard Qt
>> example (for instance: org.qtproject.example.samegame) from QtCreator it
>> tries to start the app and and after a while outputs:
>> "org.qtproject.example.samegame" died.
>>
>> Logcat shows the following log from the android device (oneplusone).
>> 
>> 01-05 15:05:33.394 25696-25696/? D/AndroidRuntime: >> START
>> com.android.internal.os.RuntimeInit uid 2000 <<
>> 01-05 15:05:33.420 25696-25696/? D/AndroidRuntime: CheckJNI is OFF
>> 01-05 15:05:33.505 25696-25696/? D/ICU: No timezone override file found:
>> /data/misc/zoneinfo/current/icu/icu_tzdata.dat
>> 01-05 15:05:33.567 25696-25696/? I/Radio-JNI:
>> register_android_hardware_Radio DONE
>> 01-05 15:05:33.595 25696-25696/? D/AndroidRuntime: Calling main entry
>> com.android.commands.am.Am
>> 01-05 15:05:33.598 1444-18680/? W/ActivityManager: Invalid packageName:
>> org.qtproject.example.samegame
>> 01-05 15:05:33.598 25696-25696/? D/AndroidRuntime: Shutting down VM
>> =
>> Invalid packageName? I'm confused.
>>
>> When using an AVD it does not work either.
>> When using the desktop kit the example app works fine.
>>
>> No problem building and running a Hello Word Standard Project with
>> Android Studio on the device.
>>
>> Here is my setup:
>>
>> Ubuntu 14.04 LTS 64bit.
>> JDK Oracle 1.8.0_101
>> NDK r10e
>> Android Studio 2.2.3 with SDK installed
>> qt-opensource-linux-x64-android-5.7.1.run
>>
>> The QtCreator android kits were automatically created.
>> The apk is successfully build for armeabi-v7a
>>
>> Any idea?
>>
>> Regards,
>> Heiko
>>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Failed first try with Qt on Android

[h...@technosis.de]

Installing the generated apk by hand on the device does work.
So it seems to be a deploying issue.

Am 05.01.2017 um 15:41 schrieb h...@technosis.de:

Hi,

I just started to evaluate Qt on Android and I'm unfortunately stuck in
the beginning. Maybe someone has a hint for me.

The problem: When running a new Hello World Project or a standard Qt
example (for instance: org.qtproject.example.samegame) from QtCreator it
tries to start the app and and after a while outputs:
"org.qtproject.example.samegame" died.

Logcat shows the following log from the android device (oneplusone).

01-05 15:05:33.394 25696-25696/? D/AndroidRuntime: >> START
com.android.internal.os.RuntimeInit uid 2000 <<
01-05 15:05:33.420 25696-25696/? D/AndroidRuntime: CheckJNI is OFF
01-05 15:05:33.505 25696-25696/? D/ICU: No timezone override file found:
/data/misc/zoneinfo/current/icu/icu_tzdata.dat
01-05 15:05:33.567 25696-25696/? I/Radio-JNI:
register_android_hardware_Radio DONE
01-05 15:05:33.595 25696-25696/? D/AndroidRuntime: Calling main entry
com.android.commands.am.Am
01-05 15:05:33.598 1444-18680/? W/ActivityManager: Invalid packageName:
org.qtproject.example.samegame
01-05 15:05:33.598 25696-25696/? D/AndroidRuntime: Shutting down VM
=
Invalid packageName? I'm confused.

When using an AVD it does not work either.
When using the desktop kit the example app works fine.

No problem building and running a Hello Word Standard Project with
Android Studio on the device.

Here is my setup:

Ubuntu 14.04 LTS 64bit.
JDK Oracle 1.8.0_101
NDK r10e
Android Studio 2.2.3 with SDK installed
qt-opensource-linux-x64-android-5.7.1.run

The QtCreator android kits were automatically created.
The apk is successfully build for armeabi-v7a

Any idea?

Regards,
Heiko

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Run script right before qmake finishes (or: embedd iOs framework)

[Richard Gustavsen]

You can try to add something like the following to your pro file:


QMAKE_POST_LINK += "cp somefile $CODESIGNING_FOLDER_PATH"


-Richard


Fra: Interest  på 
vegne av Bernhard B 
Sendt: 5. januar 2017 20:03:22
Til: interest@qt-project.org
Emne: [Interest] Run script right before qmake finishes (or: embedd iOs 
framework)

Hi,

I am currently getting the following error when compiling my Qt iOs app:

Library not loaded: @rpath 
Reason: image not found

I know that I can solve this issue by adding the framework which causes the 
problem to the "Embedded Binaries" section in my XCode project. Unfortunately, 
I currently have to do this manually every time qmake is run (as it gets 
overwritten). See also this related ticket: [1]

In one of the comments, Luke Vear mentioned his script [2] which automatically 
adds a given framework to the "Embedded Binaries" section. He does that with 
the help of a "custom process step". I really like the idea of scripting that, 
but I don't want to do this with a custom process step. The reason for that is, 
that I have many build machines, which makes it difficult to keep all the build 
configurations in sync.

So I thought about whether it's possible to modify my *:pro file in a way, that 
the script gets run automatically after everything else finished? I know that I 
can run a script with "system", but how can I make sure that it runs after 
qmake created the XCode project? Does anyone know how I can accomplish that?

Thanks for reading this,
Bernhard

[1] https://bugreports.qt.io/browse/QTBUG-51951
[2] https://github.com/lukevear/qt-xcodeproj-embeded-frameworks

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Which "Widget" technology to use when starting a new desktop app

[Uwe Rathmann]

On Thu, 05 Jan 2017 16:58:00 -0500, Mike Jackson wrote:

> After reviewing the responses and doing some more research online we
> decided to stick with the traditional QWidgets

IMO the only reasonable choice for a classic desktop application ...

> ... for our desktop app but
> get away from the QGraphics* classes and replace that older code with
> code based on QOpenGlWidget so we can get accelerated 2D rendering.

QGraphics* can also run over the OpenGL paint engine.

So as long as you need QPainter dropping QGraphics* buys you nothing - 
beside you are not happy with the quality of the implementation of this 
framework. And going away from QPainter means no more PDF export !

Concerning mixed mode ( QOpenGL + Raster ) applications. I once tried it 
an soon ran into: https://bugreports.qt.io/browse/QTBUG-50916

I don't want to say that doing pure OpenGL is the wrong decision, but 
one, that needs to be made carefully.

Uwe





___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest