[Development] Finding your way around Qt Creator code base
Hi everyone, I am working on a Qt Creator's Bug (7044) and since this is my first bug fix for Qt Creator so I am a little confused here. I have been looking at how things work in search [Find Usages and Rename Symbol Under Cursor] for two days now and I have gotten a very good idea on how is this designed. But my potential fix for the jira as per my commenthttps://bugreports.qt-project.org/browse/QTCREATORBUG-7044?focusedCommentId=187481page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-187481 needs a bit of experts' help and opinion. Main reason of my this mail is that is there a better way of finding your way through the code base. You will know what exactly am I pointing to if you check my comment on jirahttps://bugreports.qt-project.org/browse/QTCREATORBUG-7044?focusedCommentId=187481page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-187481. Also, if someone with their expertise could guide me if I am going to right direction for the fix. Thanks -- Majid Khan http://www.icplusplus.com ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Finding your way around Qt Creator code base
Thanks for that. Yea I was sure from the start that this won't be an easy task but I love it since it's helping me a lot to learn more and more. Thanks again. On Mon, Nov 12, 2012 at 9:09 PM, Ziller Eike eike.zil...@digia.com wrote: On 12 Nov 2012, at 10:40, Majid Khan mkhan3...@gmail.com wrote: Hi everyone, I am working on a Qt Creator's Bug (7044) and since this is my first bug fix for Qt Creator so I am a little confused here. I have been looking at how things work in search [Find Usages and Rename Symbol Under Cursor] for two days now and I have gotten a very good idea on how is this designed. But my potential fix for the jira as per my comment needs a bit of experts' help and opinion. Main reason of my this mail is that is there a better way of finding your way through the code base. You will know what exactly am I pointing to if you check my comment on jira. Also, if someone with their expertise could guide me if I am going to right direction for the fix. I'm adding some comments to the jira issue. You certainly haven't chosen an easy task. Br, Eike -- Eike Ziller, Senior Software Engineer - Digia, Qt Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Anja Wasenius Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B -- Majid Khan http://www.icplusplus.com ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 4.8.4 bug: mac menu bar not properly shown
Il 09/11/2012 18.48, Calogero Mauceri ha scritto: Hi, On the Mac version of my application, the menu bar is no more properly shown using the Qt 4.8.4_RC2. You can see the same problem in the mainwindows|application example. Attached are some screenshots showing the problem. The menu bar is properly working with Qt 4.8.3. Do you suggest to open a bugreport? I can confirm that this bug was introduced in Mac version of Qt 4.8.4_RC2 compiled with Carbon framework. The applicatin menu bar is properly shown with Qt 4.8.3 (Carbon framework as well). We are obliged to use Carbon framework due to this bug https://bugreports.qt-project.org/browse/QTBUG-27879 which is causing all modeless dialogs to disappear behind the main application whenever the user clicks outside them (this is a very serious problem, e.g. consider a Find/Replace dialog which always needs to be on top of the main application window). I just commited a new bug report for that problem https://bugreports.qt-project.org/browse/QTBUG-27960 Calogero -- Calogero Mauceri Software Engineer Applied Coherent Technology Corporation (ACT) www.actgate.com ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QT5 Beta 1 Android
On Android it is possible to handle display orientation by yourself, not using the default behaviour of destroying and recreating the UI. You'd use OrientationEventListener Display classes to detect the orientation then. This would make sense for a QML application where the scene graph can handle rotation of elements. The android:configChanges element in the manifest file is used to specify what things the application can handle itself. See also http://developer.android.com/guide/topics/resources/runtime-changes.html -- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. __ www.accenture.com ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QT5 Beta 1 Android
Hi all, I don't think this works very well (or at all) with NativeActivity at the moment, I put configChanges:orientation in the manifest, but android insists on restarting the NativeActivity ... for example: activity android:name=android.app.NativeActivity android:label=@string/native_activity_name android:configChanges=orientation|keyboardHidden !-- Tell NativeActivity the name of our .so -- meta-data android:name=android.app.lib_name android:value=qtqpatest/ /activity Or am I missing something? Regards, Walter On Mon, Nov 12, 2012 at 1:33 PM, shane.kea...@accenture.com wrote: On Android it is possible to handle display orientation by yourself, not using the default behaviour of destroying and recreating the UI. You’d use OrientationEventListener Display classes to detect the orientation then. This would make sense for a QML application where the scene graph can handle rotation of elements. ** ** The android:configChanges element in the manifest file is used to specify what things the application can handle itself. ** ** See also http://developer.android.com/guide/topics/resources/runtime-changes.html** ** -- -- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. __ www.accenture.com ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QT5 Beta 1 Android
On 12 November 2012 15:15, Walter Horsten walter.hors...@telenet.be wrote: Hi all, I don't think this works very well (or at all) with NativeActivity at the moment, I put configChanges:orientation in the manifest, but android insists on restarting the NativeActivity ... for example: activity android:name=android.app.NativeActivity android:label=@string/native_activity_name android:configChanges=orientation|keyboardHidden !-- Tell NativeActivity the name of our .so -- meta-data android:name=android.app.lib_name android:value=qtqpatest/ /activity Or am I missing something? Regards, Walter Necessitas does a good job with orientation, somehow. I haven't had a good look at the mechanism for it yet. On Mon, Nov 12, 2012 at 1:33 PM, shane.kea...@accenture.com wrote: On Android it is possible to handle display orientation by yourself, not using the default behaviour of destroying and recreating the UI. You’d use OrientationEventListener Display classes to detect the orientation then. This would make sense for a QML application where the scene graph can handle rotation of elements. ** ** The android:configChanges element in the manifest file is used to specify what things the application can handle itself. ** ** See also http://developer.android.com/guide/topics/resources/runtime-changes.html* *** -- -- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. __ www.accenture.com ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QT5 Beta 1 Android
Hi, It misses screenSize. android:configChanges=orientation|screenSize|keyboardHidden should work. Cheers, Laszlo On Mon, Nov 12, 2012 at 3:15 PM, Walter Horsten walter.hors...@telenet.bewrote: Hi all, I don't think this works very well (or at all) with NativeActivity at the moment, I put configChanges:orientation in the manifest, but android insists on restarting the NativeActivity ... for example: activity android:name=android.app.NativeActivity android:label=@string/native_activity_name android:configChanges=orientation|keyboardHidden !-- Tell NativeActivity the name of our .so -- meta-data android:name=android.app.lib_name android:value=qtqpatest/ /activity Or am I missing something? Regards, Walter On Mon, Nov 12, 2012 at 1:33 PM, shane.kea...@accenture.com wrote: On Android it is possible to handle display orientation by yourself, not using the default behaviour of destroying and recreating the UI. You’d use OrientationEventListener Display classes to detect the orientation then. This would make sense for a QML application where the scene graph can handle rotation of elements. ** ** The android:configChanges element in the manifest file is used to specify what things the application can handle itself. ** ** See also http://developer.android.com/guide/topics/resources/runtime-changes.html* *** -- -- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. __ www.accenture.com ___ 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] Qt 5 beta 2 packages for testing
Hi, New packages for Windows (only 32-bit), Linux and Mac are available for testing at: http://releases.qt-project.org/digia/5.0.0_beta2/backups/2012-11-12-341/ There are no known blockers in these packages, so they should be considered a candidate for Qt 5 beta 2 release, that we hope to release tomorrow (Note that win 64 is not planned to be released for Qt 5 beta 2). If you find an issue in these packages, that you believe to be a blocker. Please post a message about this on releas...@qt-project.org (in addition to creating the bugreport). Relevant information (that was mentioned previously): - The list of known issues and workarounds: http://qt-project.org/wiki/Qt500beta2KnownIssues. If you find anything that is not already there, please feel free to update the wiki with your findings. - Qt bug reports (in https://bugreports.qt-project.org/) should be reported with Affects Version/sRequired = '5.0.0 Beta 2'. - Qt Creator bug reports (in https://bugreports.qt-project.org/) should be reported with Affects Version/sRequired = 'Qt Creator 2.6.0-rc' Labels = 'creator_qt5'. Br, Sinan ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt 5 mingw build trying to link against Qt5Cored0.dll
I ran into this error while trying to build Qt 5 from git with mingw: mingw32-make[3]: Entering directory 'C:/Qt/5.0/qtbase/src/network' mingw32-make -f Makefile.Debug all mingw32-make[4]: Entering directory 'C:/Qt/5.0/qtbase/src/network' g++ -shared -Wl,--out-implib,C:\Qt\5.0\qtbase\lib\libQt5Networkd.a -o ..\..\lib\ Qt5Networkd.dll object_script.Qt5Networkd.Debug -lws2_32 -ldnsapi -ladvapi32 -L C:/Qt/5.0/qtbase/lib -lQt5Cored0 tmp\obj\debug_shared\Qt5Networkd_resource_res.o c:/mingw/bin/../lib/gcc/i686-w64-mingw32/4.7.2/../../../../i686-w64-mingw32/bin/ ld.exe: cannot find -lQt5Cored0 It seems to be looking for Qt5Cored0.dll instead of Qt5Cored.dll. Maybe some bug introduced by the lib renaming? This is from qt5 git, not the latest qtbase. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 mingw build trying to link against Qt5Cored0.dll
On segunda-feira, 12 de novembro de 2012 15.02.40, Stephen Chu wrote: It seems to be looking for Qt5Cored0.dll instead of Qt5Cored.dll. Maybe some bug introduced by the lib renaming? This is from qt5 git, not the latest qtbase. MinGW isn't in the CI, so this issue wasn't caught. Fix: https://codereview.qt-project.org/#change,39385 -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center 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
Re: [Development] QT5 Beta 1 Android
Anyway there is some duplication of effort - Bogdan, Eskil, you and Samuel, at least. (All I've done so far is test them.) So maybe it's better to sync everything up and see what are the missing pieces? On 12 November 2012 20:46, Walter Horsten walter.hors...@gmail.com wrote: It does! Splendid, this solves all the static initialization and plugins-not-unloading issues involved with the app restart. I can probably spend some time on updating the event handler to generate the proper events later this week. Thanks for the tip! On 12 Nov 2012, at 15:45, Laszlo Agocs wrote: Hi, It misses screenSize. android:configChanges=orientation|screenSize|keyboardHidden should work. Cheers, Laszlo On Mon, Nov 12, 2012 at 3:15 PM, Walter Horsten walter.hors...@telenet.be wrote: Hi all, I don't think this works very well (or at all) with NativeActivity at the moment, I put configChanges:orientation in the manifest, but android insists on restarting the NativeActivity ... for example: activity android:name=android.app.NativeActivity android:label=@string/native_activity_name android:configChanges=orientation|keyboardHidden !-- Tell NativeActivity the name of our .so -- meta-data android:name=android.app.lib_name android:value=qtqpatest/ /activity Or am I missing something? Regards, Walter On Mon, Nov 12, 2012 at 1:33 PM, shane.kea...@accenture.com wrote: On Android it is possible to handle display orientation by yourself, not using the default behaviour of destroying and recreating the UI. You’d use OrientationEventListener Display classes to detect the orientation then. This would make sense for a QML application where the scene graph can handle rotation of elements. ** ** The android:configChanges element in the manifest file is used to specify what things the application can handle itself. ** ** See also http://developer.android.com/guide/topics/resources/runtime-changes.html -- -- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. __ www.accenture.com ___ 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
Re: [Development] QT5 Beta 1 Android
On 12 Nov 2012, at 21:40, Shawn Rutledge wrote: Anyway there is some duplication of effort - Bogdan, Eskil, you and Samuel, at least. (All I've done so far is test them.) So maybe it's better to sync everything up and see what are the missing pieces? I guess that is the best way to go ... I don't know about the other work that has been done, so I'll list the main features of what I've got: - Integration in the QPA framework (normally without real issues, thanks to Laszlo). - Event handling completely using NDK functionality (keyboard event handling is limited due to NDK limitations). - Very few changes to the qt code needed. One extra static module that provides the native activity callbacks. - Launching intents via QDesktopServices. - QML, QGLContext, QBackingstore drawing is stable. - QInputInterface for the android soft-keyboard. - Very basic java class loader (which I configure via a CMake build framework) and what I haven't got: - special intent actions (like starting a phonecall, should be easy to add to the QDesktopServices code in the plugin) - multimedia plugin - sensor plugin (I have one in development, but I read QtSensors is being put on hold?) - native widgets other things I would like for the android port: - Little or no difference in code between android and desktop platforms. - Easy integration in a CMake build framework. - Transparent handling of state saving/restoring. Greetings, Walter On 12 November 2012 20:46, Walter Horsten walter.hors...@gmail.com wrote: It does! Splendid, this solves all the static initialization and plugins-not-unloading issues involved with the app restart. I can probably spend some time on updating the event handler to generate the proper events later this week. Thanks for the tip! On 12 Nov 2012, at 15:45, Laszlo Agocs wrote: Hi, It misses screenSize. android:configChanges=orientation|screenSize|keyboardHidden should work. Cheers, Laszlo On Mon, Nov 12, 2012 at 3:15 PM, Walter Horsten walter.hors...@telenet.be wrote: Hi all, I don't think this works very well (or at all) with NativeActivity at the moment, I put configChanges:orientation in the manifest, but android insists on restarting the NativeActivity ... for example: activity android:name=android.app.NativeActivity android:label=@string/native_activity_name android:configChanges=orientation|keyboardHidden !-- Tell NativeActivity the name of our .so -- meta-data android:name=android.app.lib_name android:value=qtqpatest/ /activity Or am I missing something? Regards, Walter On Mon, Nov 12, 2012 at 1:33 PM, shane.kea...@accenture.com wrote: On Android it is possible to handle display orientation by yourself, not using the default behaviour of destroying and recreating the UI. You’d use OrientationEventListener Display classes to detect the orientation then. This would make sense for a QML application where the scene graph can handle rotation of elements. The android:configChanges element in the manifest file is used to specify what things the application can handle itself. See also http://developer.android.com/guide/topics/resources/runtime-changes.html -- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. __ www.accenture.com ___ 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] potential mouse delta problem in Qt5 Beta2 on Mac OS X?
The following QML code is an example of a functional 2D knob in Qt5 Beta1. It
no longer works in Qt5 Beta2, using latest successful build from November 12.
I am on Mac OS 10.7.4 (Lion).
Perhaps something has changed and I need to recode this example knob; if so,
please advise and possibly add some information in the upcoming Qt5 Beta2
release notes if needed. Perhaps this a potential bug in Qt5 Beta2.
Additional info:
To move the knob, I use a 2-finger up-and-down- swipe on the trackpad, or I
click-and-drag a mouse up-and-down on the knob. This causes the knob to rotate
clockwise/counterclockwise. I tested this using qmlscene.)
Moving the knob result in some deprecated messages from qmlscene in Qt5 Beta1.
2012-11-12 21:52:52.063 qmlscene[23502:b03] -_continuousScroll is deprecated
for NSScrollWheel. Please use -hasPreciseScrollingDeltas.
2012-11-12 21:52:52.063 qmlscene[23502:b03] -deviceDeltaX is deprecated for
NSScrollWheel. Please use -scrollingDeltaX.
2012-11-12 21:52:52.064 qmlscene[23502:b03] -deviceDeltaY is deprecated for
NSScrollWheel. Please use -scrollingDeltaY.
In Qt5 Beta2, these messages no longer occur, and of course, the knob doesn't
move either. Maybe this is a clue to the problem?
Here is the source qml:
Knob.qml (to test, you would need to provide your own 39x39 pixel knob image
in a file named knob.png)
--
import QtQuick 2.0
Image {
id: knob
property real minimumvalue: 0
property real maximumvalue: 99
property real minimumrotation: 0
property real maximumrotation: 305
property real value: 0
width: 39
height: 39
smooth: true
Image {
id: knobImage
anchors.fill: parent
source: knob.png
rotation: knob.minimumrotation + knob.value / knob.maximumvalue *
knob.maximumrotation
smooth: true
}
MouseArea {
property int previousY: 0
anchors.fill: knobImage
onPressed: previousY = mouse.y
onPositionChanged: {
var delta = (previousY - mouse.y) * 1.00
if (knob.value + delta knob.maximumvalue) {
knob.value = knob.maximumvalue
}
else if (knob.value + delta knob.minimumvalue) {
knob.value = knob.minimumvalue
}
else {
knob.value += delta
previousY = mouse.y
}
}
}
}
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] potential mouse delta problem in Qt5 Beta2 on Mac OS X?
I guess it's related with this change, adb156e4dd64609ba6c0b172e9c428a79e306a7c
https://codereview.qt-project.org/37451
Regards,
Liang
From: development-bounces+liang.qi=digia@qt-project.org
[development-bounces+liang.qi=digia@qt-project.org] on behalf of VStevenP
[vstevenpa...@yahoo.com]
Sent: Tuesday, November 13, 2012 4:20 AM
To: development@qt-project.org
Subject: [Development] potential mouse delta problem in Qt5 Beta2 on Mac OS X?
The following QML code is an example of a functional 2D knob in Qt5 Beta1. It
no longer works in Qt5 Beta2, using latest successful build from November 12.
I am on Mac OS 10.7.4 (Lion).
Perhaps something has changed and I need to recode this example knob; if so,
please advise and possibly add some information in the upcoming Qt5 Beta2
release notes if needed. Perhaps this a potential bug in Qt5 Beta2.
Additional info:
To move the knob, I use a 2-finger up-and-down- swipe on the trackpad, or I
click-and-drag a mouse up-and-down on the knob. This causes the knob to rotate
clockwise/counterclockwise. I tested this using qmlscene.)
Moving the knob result in some deprecated messages from qmlscene in Qt5 Beta1.
2012-11-12 21:52:52.063 qmlscene[23502:b03] -_continuousScroll is deprecated
for NSScrollWheel. Please use -hasPreciseScrollingDeltas.
2012-11-12 21:52:52.063 qmlscene[23502:b03] -deviceDeltaX is deprecated for
NSScrollWheel. Please use -scrollingDeltaX.
2012-11-12 21:52:52.064 qmlscene[23502:b03] -deviceDeltaY is deprecated for
NSScrollWheel. Please use -scrollingDeltaY.
In Qt5 Beta2, these messages no longer occur, and of course, the knob doesn't
move either. Maybe this is a clue to the problem?
Here is the source qml:
Knob.qml (to test, you would need to provide your own 39x39 pixel knob image
in a file named knob.png)
--
import QtQuick 2.0
Image {
id: knob
property real minimumvalue: 0
property real maximumvalue: 99
property real minimumrotation: 0
property real maximumrotation: 305
property real value: 0
width: 39
height: 39
smooth: true
Image {
id: knobImage
anchors.fill: parent
source: knob.png
rotation: knob.minimumrotation + knob.value / knob.maximumvalue *
knob.maximumrotation
smooth: true
}
MouseArea {
property int previousY: 0
anchors.fill: knobImage
onPressed: previousY = mouse.y
onPositionChanged: {
var delta = (previousY - mouse.y) * 1.00
if (knob.value + delta knob.maximumvalue) {
knob.value = knob.maximumvalue
}
else if (knob.value + delta knob.minimumvalue) {
knob.value = knob.minimumvalue
}
else {
knob.value += delta
previousY = mouse.y
}
}
}
}
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
