Re: [Development] Question regarding recent commit 'Fix double click handling.'
Hi Jon, Yes, good catch, the built-in timestamping of QWindowSystemInterface is broken due to the lack of a call to start() or restart(). This affects mouse and touch events generated by plugins that do not provide their own timestamps. The patch looks good although we may want to consider switching to QElapsedTimer. But that's something for another patch. Regards, Laszlo -Original Message- From: development-bounces+laszlo.p.agocs=nokia@qt-project.org [mailto:development-bounces+laszlo.p.agocs=nokia@qt-project.org] On Behalf Of ext Jon Trulson Sent: 09 March 2012 01:19 To: development@qt-project.org Subject: [Development] Question regarding recent commit 'Fix double click handling.' regarding commit id: b371f3f943703840d0dfbe30505018bcca06e260 I guess this question is for you Laszlo. About a week or so ago, I discovered a problem with mouse handling (arm board, eglfs, using evdevmouse plugin). I found that every other mouse press event (with no intervening movement) would get lost. Digging deeper, I found that the event timer (QWindowSystemInterfacePrivate::eventTime) in qwindowsysteminterface_qpa.cpp is never actually .start()'ed. This results in all eventTime.elapsed() calls returning 0, and therefore any comparisons against the event's timestamp in other places (like the doubleclick logic) to be meaningless (since they are all always 0). I submitted a change request: http://codereview.qt-project.org/18482 that did fix the missing button event problem, by ensuring that the timer is actually started. I didn't know who to ask to review, but maybe you are the one? At any rate, with your fixes (the above mentioned commit) and my fix removed as a test, I no longer miss mouse button events. However, every other click now generates a doubleclick event, which is wrong. Re-adding my fix seems to work correctly - I only get doubleclicks events when I actually doubleclick. So - while my fix may not be the best place to start the timer, it is still needed in some fashion - the timer has to be started somewhere for this logic to ever work properly... Can this change request get reviewed or laughed at? Thanks. -- Jon Trulson Get the cheese to sickbay, the Doctor should look at it as soon as possible. -- Chief Engineer B'Elanna Torres, Voyager ___ 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] Qt Playground - Command Line Parser experiment
On Fri, Mar 09, 2012 at 01:36:07AM +0200, ext Laszlo Papp wrote: It is not a separate module, but class(es). The name for this experiment, in playground, it's entirely misguided to create a playground project for classes (which are presumably meant to end up in qtcore). what you should be requesting is an official feature branch. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt 4.8.1 open source release date approaching..
Hi, We are currently preparing testing Qt 4.8.1 open source release for next week. Exact release date is still open, until all tests are passed. And, as discussed it is possible that critical problems are found, and then we need to take another try. We are currently testing against sha1 that points to commit: 1e0021d8d9e374ae3959fcd4eac5d9e7238cbc54 Latest version of changes-4.8.1 file is found attached. Again, this may not yet be the final one, we need to first test. In addition to the testing we are conducting, it is good to hear user feedback. So, please feel free to test and send feedback to releas...@qt-project.orgmailto:releas...@qt-project.org mailing list. Br, Akseli Akseli Salovaara Software Specialist, Qt Commercial RD DIGIA Plc Piippukatu 11, FI-40101 Jyväskylä Finland Email: akseli.salova...@digia.commailto:akseli.salova...@digia.com Visit us at: www.digia.comhttp://www.digia.com/ or qt.digia.com -- PRIVACY AND CONFIDENTIALITY NOTICE This message and any attachments are intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error, please contact the sender immediately and delete the message and any attachments accompanying it. DIGIA Plc does not accept liability for any corruption, interception, amendment, tampering or viruses occurring to this message. -- changes-4.8.1_proposal Description: changes-4.8.1_proposal ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt Playground - Command Line Parser experiment
On Thursday 08 March 2012 20:36:07 Laszlo Papp wrote: Hi, I would like to experiment with a command line parser in Qt Playground. The topic and the use case were more or less discussed previously on the qt5-feedback mailing list around last October. It is not a separate module, but class(es). The name for this experiment, in playground, would be something like Command Line Parser. According to the regulation: if nobody objects to this addition from the beginning, I need to get the support of one existing module maintainer in order to be able to experiment with this feature in playground. I was doing some experiment with this here: https://github.com/hugopl/qcmdlineparser If you want, we would join our efforts. Either way, please let me know your thoughts. Thank you in advance! Best Regards, Laszlo Papp ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development -- Hugo Parente Lima INdT - Instituto Nokia de Tecnologia 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] where can I get the lastest source code?
now the Qt4 version is not developed? and I only get the lastest version from git://gitorious.org/qt/qtbase.git ?? The Qt4 repository is still at git://gitorious.org/qt/qt.git Bug fixes can still go there for 4.8.x patch releases. The modular repositories (e.g. qtbase) are only for Qt5 onwards. Subject to local law, communications with Accenture and its affiliates including telephone calls and emails (including content), may be monitored by our systems for the purposes of security and the 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] [Releasing] Qt 4.8.1 open source release date approaching..
Hi, 2012/3/9 Salovaara Akseli akseli.salova...@digia.com: Hi, We are currently preparing testing Qt 4.8.1 open source release for next week. Exact release date is still open, until all tests are passed. And, as discussed it is possible that critical problems are found, and then we need to take another try. We are currently testing against sha1 that points to commit: 1e0021d8d9e374ae3959fcd4eac5d9e7238cbc54 Can you create a branch instead? The way it's been done traditionally (for old values of tradition) is: a. Create a 4.8.1 branch. People should be testing this branch for the release and this branch only. b. Patches can continue to go in 4.8 branch (but will only be in 4.8.2). The testing of the above doesn't need to be restarted over and over again c. If the committer in 4.8 feels his patch is supremely important and fit for 4.8.1, he pings the release dude (you) and seeks permission to put his change in 4.8.1 branch. You analyze the risk and approve/disapprove. d. Once you are ready for release, ship the 4.8.1 branch. Create a signed tag v4.8.1 with your signature. This makes sure that even if someone confidently committed stuff in 4.8.1 post-release, we still know what we shipped with. If there's another methodology in place, let me know, but the current way of sha1 based testing is not ideal. Girish ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] QtSerialPort addon Wiki. Need spelling checking for English.
Hi all. I created a Wiki page for the addon QtSerialPort https://qt-project.org/wiki/QtSerialPort and I need help with spelling of English. Help ме please. Best regards, Denis ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Marketing] GSoC 2012
Hi, The deadline is now in 7 hours (23:00 UTC) As a student perspective, I would really be enthusiast working on the Qt Project, and I think it definitely should be sent for approval to the GSoC 2012. However, the project needs mentors. Nokia employees seem to have been removed from the mentors list, why ? Currently, the wiki lists two mentors, but we need more. Furthermore, if you want the project to enter the GSoC, some paperwork needs to be done, and we have to hurry up. Com'on guys, the Qt project is a great project, and I'm sure many students would love getting involved on it (including me) :) -Original Message- From: development-bounces+mathieu.stefani=supinfo@qt-project.org [mailto:development-bounces+mathieu.stefani=supinfo@qt-project.org] On Behalf Of Giuseppe D'Angelo Sent: jeudi 1 mars 2012 09:22 To: daniel.molken...@nokia.com Cc: development@qt-project.org Subject: Re: [Development] [Marketing] GSoC 2012 Hi, If you want to mentor a project or if you have a proposal to make, please sign up at http://wiki.qt-project.org/GSOC_Proposals. Although there hasn't been much discussion, I'm happy to see that some proposals are being made :-) Just for the records: some ancient proposals from some year ago are available here http://web.archive.org/web/20100606041700/http://groups.google.com/group/qt-gsoc/web/project-ideas Cheers, -- Giuseppe D'Angelo ___ 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] QRegExp::W3CXmlSchema11 problems
Hi, I'm working on a QRegExp::operator QRegularExpression() implementation so that we can remove QRegExp from public API (reducing the breakages to a minimum -- hopefully nobody was actually using implicit conversions for those methods, and the QRegExp constructor is explicit). But I'm having an hard time figuring out how to properly port regexps in the W3CXmlSchema11 syntax. This particular syntax is supposed to make use of XSD 1.1 regexps, described in [1]. They're Perl-like regexps with some significant differences, for instance: - no lazy quantifiers - support for character class subtraction: [a-z-[aeiou-[b-k]]] - new multi-character escapes like \i and \c - ordinary multi-character escapes (like \w , \s , etc.) matching different Unicode subsets - etc. Now the problem is that the support for this syntax inside QRegExp is quite broken: character class subtraction isn't supported, \i and \c don't match what they're supposed to match, the other multi-character escapes don't match the right Unicode subsets. This particular syntax has *never* been tested in Qt (I added the very first test in Qt5 some days ago), and the only two occurrences of its usage I can find are qtbase/examples/tools/regexp/regexpdialog.cpp:71: syntaxComboBox-addItem(tr(W3C Xml Schema 1.1), QRegExp::W3CXmlSchema11); qtxmlpatterns/src/xmlpatterns/functions/qpatternplatform.cpp:200: QRegExp retval(rewrittenPattern, Qt::CaseSensitive, QRegExp::W3CXmlSchema11); Therefore, I'm wondering if it's worth spending more time in writing down a proper XSD - Perl regexp conversion routine (like I'm currently doing) and not ditch XSD regexps at all in the QRegExp - QRegularExpression conversion. Any thoughts? (For the records, the support was added by commit 210bd7b in Qt 4 [2], but I don't know the rationale of the whole feature and the commit message doesn't tell anything. Was it just for the xmlpatterns module?) -- Giuseppe D'Angelo [1] http://www.w3.org/TR/xmlschema-2/#regexs [2] http://qt.gitorious.org/qt/qt/commit/210bd7b6033e41aad61fe131002dc5e496d7427a ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Releasing] Qt 4.8.1 open source release date approaching..
On Fri, Mar 09, 2012 at 07:16:24PM +, ext shane.kea...@accenture.com wrote: (rc1)-o-o-o-o-o-o-fix-o-o-o-o-o-o-fix \ fix(rc2)-fix(v4.8.1) this is no option, because it loses the tag from the history. traditionally we have merged back the release branch to the maintenance branch (and thus to master), which means that we have all those cherry-picks twice in the history. try to read *that*. therefore the only clean options are either a) just don't create a branch or b) if you create a branch, then apply any fixes which are supposed to be in it *only* to that branch, so it can be cleanly forward-merged. It was pointed out that branches in git are cheap, branches are cheap is a bogus argument to start with. it's always the merging that incurrs the cost (on the human side. technically broken scms are not worth mentioning). ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Marketing] GSoC 2012
On 09/03/2012 10:07, ext STEFANI Mathieu wrote: The deadline is now in 7 hours (23:00 UTC) As a student perspective, I would really be enthusiast working on the Qt Project, and I think it definitely should be sent for approval to the GSoC 2012. However, the project needs mentors. Nokia employees seem to have been removed from the mentors list, why ? Unfortunately, after a thorough evaluation of the GSoC 2012 MOPA (Mentor Organization Participation Agreement), Nokia employees are not able to participate in this year GSoC. The details on the reasoning is unbeknownst to me. Sorry. -- .marius Currently, the wiki lists two mentors, but we need more. Furthermore, if you want the project to enter the GSoC, some paperwork needs to be done, and we have to hurry up. Com'on guys, the Qt project is a great project, and I'm sure many students would love getting involved on it (including me) :) -Original Message- From: development-bounces+mathieu.stefani=supinfo@qt-project.org [mailto:development-bounces+mathieu.stefani=supinfo@qt-project.org] On Behalf Of Giuseppe D'Angelo Sent: jeudi 1 mars 2012 09:22 To: daniel.molken...@nokia.com Cc: development@qt-project.org Subject: Re: [Development] [Marketing] GSoC 2012 Hi, If you want to mentor a project or if you have a proposal to make, please sign up at http://wiki.qt-project.org/GSOC_Proposals. Although there hasn't been much discussion, I'm happy to see that some proposals are being made :-) Just for the records: some ancient proposals from some year ago are available here http://web.archive.org/web/20100606041700/http://groups.google.com/group/qt-gsoc/web/project-ideas Cheers, ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Marketing] GSoC 2012
Unfortunately, after a thorough evaluation of the GSoC 2012 MOPA (Mentor Organization Participation Agreement), Nokia employees are not able to participate in this year GSoC. The details on the reasoning is unbeknownst to me. Sorry. I then infer that the Qt Project won't enter this year GSoC. Sad news. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QDoc can't ignore Q_PROPERTY
Just to make sure everybody understands: With this change applied all NOTIFY properties that are currently documented will not be documented anymore. If there are no objections before coming Tuesday (13 March) 09:00 Oslo time I will put this patch in. Casper From: Ramsay Lincoln (Nokia-MP/Brisbane) Sent: Friday, March 09, 2012 12:37 AM To: Vandonderen Casper (Nokia-MP/Oslo) Cc: ext Girish Ramakrishnan; development@qt-project.org Subject: Re: [Development] QDoc can't ignore Q_PROPERTY On 03/08/2012 07:38 PM, Vandonderen Casper (Nokia-MP/Oslo) wrote: It might be that this was indeed an oversight. Can you create a bug report and assign it to me (I am not promising I have time to fix it now, or you can fix qdoc yourself and add me as reviewer ;-) ) Ok... The fix is (as far as I can tell) a single line of code. With that in place, NOTIFY signals are handled the same as getters and setters for properties. Perhaps most significantly, documentation for the signal is silently ignored by qdoc. While trying to find that line, I found two other bits of code dealing with getters and setters but not notifiers. I've updated them too but I don't actually know what they do. http://codereview.qt-project.org/#change,19374 -- Lincoln Ramsay - Senior Software Engineer Qt Development Frameworks, Nokia - http://qt.nokia.com/ ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
