Re: [Development] Patches for QPA KMS
Try running qwindow-compositor with -plugin EvdevMouse -plugin EvdevKeyboard Cheers, Laszlo From: development-bounces+laszlo.p.agocs=nokia@qt-project.org [development-bounces+laszlo.p.agocs=nokia@qt-project.org] on behalf of ext Pier Luigi [pierluigi.fior...@gmail.com] Sent: Wednesday, July 25, 2012 9:07 AM To: Elvis Lee Cc: development@qt-project.org Subject: Re: [Development] Patches for QPA KMS 2012/7/19 Elvis Lee kwangwoong@lge.com: I know that kms is not included in configure yet. But I have used it for developing with qtwayland. Few days ago, I did update qtwayland, mesa and others. Then, I found that the kms didn’t work well. So I made two patches and tested in my environment. Could you review that? Can't review it but I tested it yesterday. Some days I ago I had an error trying to run the qwindow-compositor on VMware Fusion, using Mesa from git (from 2012-07-02): libEGL debug: Native platform type: drm (environment overwrite) libEGL debug: EGL search path is /system/lib/egl libEGL debug: added egl_dri2 to module array libEGL debug: the best driver is DRI2 kms initialized with geometry QRect(0,0 2560x1600) created gbm surface 0x14f8600 2560 1600 created window surface Mesa warning: couldn't open libtxc_dxtn.so, software DXTn compression/decompression unavailable Failed to retrieve the get_egl_context function Failed to initialize egl display And the compositor wasn't working. The error doesn't show up anymore using your patch and it works, tested on a HD2000 Sandy Bridge machine. Now I can run the QtWayland compositor although it doesn't show the background until I start an application and mouse and keyboard input is not accepted. Is it something still missing on this plugin (like evdev support)? -- Don't let the noise of other's opinions drown out your own inner voice. (Steve Jobs) ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] 4.8 flickable versus mousearea drag fix
On 07/24/2012 09:01 PM, Rick Stockton wrote: Hi. This is WRT fix https://codereview.qt-project.org/#change,30222,patchset=2 for 4.8 declarative. The changeset allows drag actions to occur with more 2D freedom, but it steals the mouse (and prevents stealing by the parent flickable) in order to do so. I don't think that the patch does anything evil to the grab. Even without it, you can still drag an item in a direction perpendicular to the flickable's axis. The only thing that the patch does is that it makes it possible to change the Drag.axis while the drag is still occurring; so that, for instance, once a ListView item has been dragged away from the parent ListView, we can allow it to be dragged everywhere on the screen. The issue is described here: https://bugreports.qt-project.org/browse/QTBUG-26440 Just try running the attached drag.qml file before and after the fix. Ciao, Alberto -- http://blog.mardy.it - geek in un lingua international! ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QFileSystemWatcher and Recursive Monitoring
On 25/07/2012 00:29, ext Laszlo Papp wrote: On Tue, Jul 24, 2012 at 11:59 PM, marius.storm-ol...@nokia.com wrote: 4) put the functionality in an add-on, which has no requirement of supporting all platforms Really? Was a community decision agreed upon about that earlier? Perhaps I have just missed something, but as an official Qt Project add-on, I would expect a bit more as a developer using that add-on. Perhaps plugin architecture can help or so, with such cases? This important information is not documented here either: http://qt-project.org/wiki/Creating-a-new-module-or-tool-for-Qt If it is like that, perhaps it should be. I may not be the only person whom it makes wondering. :-) I'm not quite sure what information you are missing on that page? I didn't specify if it should be a playground project or not. No matter if it's playground or not, both versions are add-ons which other may include in their builds if they want the functionality. Neither playground nor non-playground add-ons need to support all platforms, though if they want to be in the Qt Essentials set of modules, they do. -- .marius ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QFileSystemWatcher and Recursive Monitoring
I'm not quite sure what information you are missing on that page? The information about expectations and requirements about an add-on, for sure. There should be mentionings there for new contributors joining the project through playground for instance, or at least a link to such a page from the aforementioned. Neither playground nor non-playground add-ons need to support all platforms, though if they want to be in the Qt Essentials set of modules, they do. Is that documented somewhere? I have not personally seen any such a discussion on this mailing list. Best Regards, Laszlo Papp ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QFileSystemWatcher and Recursive Monitoring
It predates the list. It's one of the grandfathered principles of the Qt Project: the essentials work everywhere, in all Reference Platforms. Any feature contributed to them must support all Reference Platforms before it can be considered for acceptance. That I am aware of, for sure. However, my default understanding was the same about the add-on modules, which is apparently not right. It would be nice to see this documented, if it is not yet done. Best Regards, Laszlo Papp ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QFileSystemWatcher and Recursive Monitoring
On 25/07/2012 05:52, ext Thiago Macieira wrote: On quarta-feira, 25 de julho de 2012 11.45.23, Laszlo Papp wrote: Neither playground nor non-playground add-ons need to support all platforms, though if they want to be in the Qt Essentials set of modules, they do. Is that documented somewhere? I have not personally seen any such a discussion on this mailing list. It predates the list. It's one of the grandfathered principles of the Qt Project: the essentials work everywhere, in all Reference Platforms. Any feature contributed to them must support all Reference Platforms before it can be considered for acceptance. It's also stated in a bit roundabout way. If you look at http://qt-project.org/wiki/Qt-Essentials-Modules it'll say The Qt Essentials modules are mandatory in all platforms. while the same is not stated on the http://qt-project.org/wiki/Qt-Add-ons-Modules it says Add-ons can be included optionally in Qt enabled platforms. So, it already says that that Essentials works on all platforms, while add-ons may only work on some. And many of the previous Qt Mobility modules only have backends that work on some platforms, for example. -- .marius ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QFileSystemWatcher and Recursive Monitoring
Nice. I have missed that. :-) Thank you for your help. Best Regards, Laszlo Papp On Wed, Jul 25, 2012 at 12:03 PM, marius.storm-ol...@nokia.com wrote: On 25/07/2012 05:52, ext Thiago Macieira wrote: On quarta-feira, 25 de julho de 2012 11.45.23, Laszlo Papp wrote: Neither playground nor non-playground add-ons need to support all platforms, though if they want to be in the Qt Essentials set of modules, they do. Is that documented somewhere? I have not personally seen any such a discussion on this mailing list. It predates the list. It's one of the grandfathered principles of the Qt Project: the essentials work everywhere, in all Reference Platforms. Any feature contributed to them must support all Reference Platforms before it can be considered for acceptance. It's also stated in a bit roundabout way. If you look at http://qt-project.org/wiki/Qt-Essentials-Modules it'll say The Qt Essentials modules are mandatory in all platforms. while the same is not stated on the http://qt-project.org/wiki/Qt-Add-ons-Modules it says Add-ons can be included optionally in Qt enabled platforms. So, it already says that that Essentials works on all platforms, while add-ons may only work on some. And many of the previous Qt Mobility modules only have backends that work on some platforms, for example. -- .marius ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Patches for QPA KMS
Turns out there are a number of issues here and there which prevent keyboard input from working in qwindow-compositor when running on kms and evdevkeyboard. However, once changes 31458, 31491, 31475, 31476 and 31480 get merged to qtbase and qtwayland, it should start to function properly (incl. the initial showing of the background image). Cheers, Laszlo From: development-bounces+laszlo.p.agocs=nokia@qt-project.org [development-bounces+laszlo.p.agocs=nokia@qt-project.org] on behalf of Agocs Laszlo.P (Nokia-MP/Tampere) Sent: Wednesday, July 25, 2012 11:13 AM To: pierluigi.fior...@gmail.com Cc: development@qt-project.org Subject: Re: [Development] Patches for QPA KMS Try running qwindow-compositor with -plugin EvdevMouse -plugin EvdevKeyboard Cheers, Laszlo From: development-bounces+laszlo.p.agocs=nokia@qt-project.org [development-bounces+laszlo.p.agocs=nokia@qt-project.org] on behalf of ext Pier Luigi [pierluigi.fior...@gmail.com] Sent: Wednesday, July 25, 2012 9:07 AM To: Elvis Lee Cc: development@qt-project.org Subject: Re: [Development] Patches for QPA KMS 2012/7/19 Elvis Lee kwangwoong@lge.com: I know that kms is not included in configure yet. But I have used it for developing with qtwayland. Few days ago, I did update qtwayland, mesa and others. Then, I found that the kms didn’t work well. So I made two patches and tested in my environment. Could you review that? Can't review it but I tested it yesterday. Some days I ago I had an error trying to run the qwindow-compositor on VMware Fusion, using Mesa from git (from 2012-07-02): libEGL debug: Native platform type: drm (environment overwrite) libEGL debug: EGL search path is /system/lib/egl libEGL debug: added egl_dri2 to module array libEGL debug: the best driver is DRI2 kms initialized with geometry QRect(0,0 2560x1600) created gbm surface 0x14f8600 2560 1600 created window surface Mesa warning: couldn't open libtxc_dxtn.so, software DXTn compression/decompression unavailable Failed to retrieve the get_egl_context function Failed to initialize egl display And the compositor wasn't working. The error doesn't show up anymore using your patch and it works, tested on a HD2000 Sandy Bridge machine. Now I can run the QtWayland compositor although it doesn't show the background until I start an application and mouse and keyboard input is not accepted. Is it something still missing on this plugin (like evdev support)? -- Don't let the noise of other's opinions drown out your own inner voice. (Steve Jobs) ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] [Announce] Qt Creator 2.5.1 released
We just released Qt Creator 2.5.1 ! Blog: http://labs.qt.nokia.com/2012/07/25/qt-creator-2-5-1-released/ Download: http://qt-project.org/wiki/Qt_Creator_Releases Br, The Qt Creator Team -- Eike Ziller Principal Software Engineer Nokia, Qt Development Frameworks Nokia gate5 GmbH Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B Umsatzsteueridentifikationsnummer: DE 812 845 193 Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori ___ Announce mailing list annou...@qt-project.org http://lists.qt-project.org/mailman/listinfo/announce ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Announce] Qt Creator 2.5.1 released
On 7/25/12 8:23 AM, List for announcements regarding Qt releases and development wrote: We just released Qt Creator 2.5.1 ! Blog: http://labs.qt.nokia.com/2012/07/25/qt-creator-2-5-1-released/ Download: http://qt-project.org/wiki/Qt_Creator_Releases Br, The Qt Creator Team The debug helper fails to build on Mac with Qt 5. Replacing dumpper.cpp from git master fixes it. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Multitouch on top of XInput 2.2
On 07/09/2012 07:42 PM, Shawn Rutledge wrote: On Thursday wk26 2012 June 28 05:09:41 PM ext Shawn Rutledge wrote: On 28 June 2012 13:03, Christian Spielberger c.spielber...@bct-electronic.com wrote: Hi, I got multitouch on top of XInput 2.2 to work. See http://www.youtube.com/watch?v=sRSC4CEYmIg ! Repo: See https://gitorious.org/~cspiel/qt/cspiels-qt-4_8-with-xinput2_1 ! Branch: 4.8-XI2.2-touch Maybe the branch can be the base for the multitouch integration for X11. Excellent! I was planning to work on Qt 5 support for XI 2.2 soon, so that should be helpful. However due to the way the code has been rearranged, the patch will be in different files anyway. Would you like to convert your changes into a patch on gerrit so it can be reviewed to go into 4.8.x? I can also test it on a couple of devices. My patch for Qt 5 is here: https://codereview.qt-project.org/#change,30469 Hi Shawn, I tried to commit my branch to gerrit following this procedure. 1. Made a new branch from current 4.8 which rests here: https://qt.gitorious.org/~cspiel/qt/cspiels-qt-4_8-with-xinput2_1/commits/4.8-XI2.2 2. Merged with git://gitorious.org/+qt-developers/qt/multipoint-touch.git branch refs/heads/master 3. Applied my changes with git cherry-pick. 4. Set up the gerrit account. In my .git/config I have: [remote gerrit] url = csp...@codereview.qt-project.org:qt/qt fetch = +refs/heads/*:refs/remotes/gerrit/* [branch gerrit_4.8] remote = gerrit merge = refs/for/4.8 5. Changed to gerrit_4.8 locally and merged with 4.8-XI2.2 6. git push gives: $ git push Counting objects: 422, done. Delta compression using up to 8 threads. Compressing objects: 100% (133/133), done. Writing objects: 100% (377/377), 62.46 KiB, done. Total 377 (delta 317), reused 269 (delta 244) remote: Resolving deltas: 14% (45/317) remote: remote: ERROR: In commit 408021665e7a6b393b9aad3b911411ca02f7186b remote: ERROR: committer email address thiago.macie...@nokia.com remote: ERROR: does not match your user account. remote: ERROR: remote: ERROR: The following addresses are currently registered: remote: ERROR:c.spielber...@bct-electronic.com remote: ERROR: remote: ERROR: To register an email address, please visit: remote: ERROR: https://codereview.qt-project.org/#settings,contact remote: remote: To csp...@codereview.qt-project.org:qt/qt ! [remote rejected] gerrit_4.8 - refs/for/4.8 (invalid committer) error: failed to push some refs to 'csp...@codereview.qt-project.org:qt/qt' Which makes sense since the commit 408021665 is originally from repo multipoint-touch.git. This commit is from Bradley T. Hughes bradley.hug...@nokia.com. So the email addr thiago.macie...@nokia.com makes no sense, but it makes sense that I can not submit this to gerrit. What I want is to suggest the changes in the multipoint-touch.git repo plus my changes to be reviewed/merged into 4.8 mainline. How such a situation should be handled (with gerrit)? regards, chris. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Multitouch on top of XInput 2.2
On quarta-feira, 25 de julho de 2012 17.29.47, Christian Spielberger wrote: What I want is to suggest the changes in the multipoint-touch.git repo plus my changes to be reviewed/merged into 4.8 mainline. How such a situation should be handled (with gerrit)? It cannot be. Qt 4.8 will not support XInput 2.2, since that would be a new feature. You're welcome to keep your branch elsewhere and link to it from the website, so people know to find it. But they need to understand that it's not official and the Qt Project cannot support it. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center Intel Sweden AB - Registration Number: 556189-6027 Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] No more Qt5 beta snapshot for mac since 2012-07-17_07-01-32?
Hi, Just mailing to the list incase nobody noticed it. http://releases.qt-project.org/qt5.0/beta-snapshots/ Last one with a Mac snapshot is from 2012-07-17 Which i'm downloading right now. I hope it runs on Mountain Lion :) Cheers, Mark ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
