Re: [Development] Proposal: Adding dependency injection to Qt

t; added to Qt. > > Let me know your opinion on that. > > BR > Hamed Masafi > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development > -- Filippo Cucchetto ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] Pointer handlers: transparent or block? was Re: QEvent::accept() vs. the newer event delivery algorithms in Qt Quick; remaining API issues; etc.

> interaction between the new flag and TapHandler.gesturePolicy is tricky > though. One will have to override the other. I suppose maybe blocking > should override gesturePolicy because blocking is the geekier flag, you > probably know what you’re doing if you use it? But I didn’t try yet; maybe > something would go wrong with that. > > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development -- Filippo Cucchetto ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] QProperty and when evaluation occurs

That said if something like that exists it means that given a chain of QProperties it need just one "immediate" observers to break all the "benefits" of lazy evaluation(given that it causes all the chain to recompute). This obviously is not worse tha

Re: [Development] QProperty and when evaluation occurs

end an email/message after an alarm has been triggered That said yes, you can can workaround this limitation through polling be it a QTimer(0) or whatever -- Filippo Cucchetto ___ Development mailing list Development@qt-project.org https://lists

Re: [Development] QProperty and when evaluation occurs

ibly > along the lines of QSingleShot(0))? > > This assumes part of the intent is to enable QObjects with derived properties > at an interface level... > > Thoughts? > > Regards, > Brett > _____

Re: [Development] QProperty and library coding guide

to display that value on a QQuick Text item and someone change the height or the width? Who is in charge to triggered the "read" of the property? Alternative solution with Qt5 tech: use QSize and change both width/height atomically. -- Filippo Cucchetto

Re: [Development] [Qt-creator] Stepping down as maintainer of the CMake plugin of Qt Creator

t; Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho. Sitz der > Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 > B > ___ > Qt-creator mailing list > qt-crea...@qt-project.org > https://lists.qt-proje

Re: [Development] Changes to Qt offering

this is not how it works. I'm talking for myself. I wouldn't pay more that $600 yearly (per dev). Again the announced offer (500$) is not very different from my conclusion. -- Filippo Cucchetto Il giorno mer 29 gen 2020 alle ore 23:37 Konstantin Shegunov ha scritto: > > > >

Re: [Development] QtCS2019 Notes from "Branch Policy" discussion

ess in backporting. > > > Cheers, > Volker > > Thank you for the explanations -- Filippo Cucchetto ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] QtCS2019 Notes from "Branch Policy" discussion

n rare cases; and we don't handle > > hot-fixes any differently than change files. Simple rules are easy to > follow. > > > > Eddy. > > > > Updating the JIRA ticket with this concise summary from Eddy, we can start > implementing the tooling su

Re: [Development] QTCS2019 Notes from QtQml session

want speed? use plain C++. Il giorno lun 25 nov 2019 alle ore 22:06 Filippo Cucchetto < filippocucche...@gmail.com> ha scritto: > @Ekke > I think you should redesign your qml the other way around. For your > problem there're multiple solutions > 1) Use some sort of StackView.view

Re: [Development] QTCS2019 Notes from QtQml session

__ > > Development mailing list > > Development@qt-project.org > > https://lists.qt-project.org/listinfo/development > > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development > -- Filippo Cucchetto ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] Stepping down as maintainer of project management in Qt Creator

I would like to thank you for all your hard work and reviews. F. Il giorno Mer 19 Dic 2018, 16:51 Tobias Hunger ha scritto: > Hello everybody, > > not having lived up to the role of maintainer of the project management > code in Qt Creator for a while now, I would like to formally step down. >

Re: [Development] How is Quick Controls 2 deployment meant to be ?

ts. Maybe I'm really missing something > obvious that I couldn't find in the online documentation. > > Cheers, > Massimo > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > -- Filippo Cucchetto ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Adding std::weak_ptr to QModelIndex

2017-04-21 9:13 GMT+02:00 Marc Mutz <marc.m...@kdab.com>: > On Friday 21 April 2017 08:42:37 Filippo Cucchetto wrote: > > Is there any plan to enhance the QModelIndex interface by adding support > to > > std::weak_ptr<void? > > I know that is not necessary si

Re: [Development] Branch request: wip/itemviews in qtdeclarative

nokia.com> > > Yeah sounds like I’d better look at a few of those. > > _______ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > -- Filippo Cucchetto ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] A new approach for Qt main()

Does this relates to moving Qt main loop to a different thread other than the main thread? Cause currently creating the QtApp from a different thread causes problems. In particular the plugins static objects are destroyed at app exit and thus on the main thread (and this causes problems because

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

(imho this could be harder by email). Given that i'm ok in both codereview or email...maybe i'm too biased by github :) 2016-09-20 21:26 GMT+02:00 Thiago Macieira <thiago.macie...@intel.com>: > On terça-feira, 20 de setembro de 2016 19:04:07 PDT Filippo Cucchetto wrote: >> Reall

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

ftware Architect - Intel Open Source Technology Center > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development -- Filippo Cucchetto ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Input events handling ideas and feedback

g/tunneling and who raised the event. > Aha… so bubbling doesn’t always occur: For what i see bubbling always happen if the event has not been pre filtered by tunneling. In this case the event bubble up until it gets accepted. After being accepted the bubbling continue iff there'are items who wha

Re: [Development] Input events handling ideas and feedback

ndling (like is done with the Keys attached objects). In this way we can disable the item default event handling with already handled events (that bubbled up from a delegate). Thank you again for the answer F. 2016-06-27 10:39 GMT+02:00 Shawn Rutledge <shawn.rutle...@qt.io>: > >

Re: [Development] Input events handling ideas and feedback

t is recommended for us users: better starting off with widgets > for new desktop applications ? > > Uwe > > > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/de

Re: [Development] ListView and spaces QTBUG-46488

ent@qt-project.org>: > > This can also be reproduced with ListView instead of TreeView: > > https://bugreports.qt.io/browse/QTBUG-53263 > > Thanks, > > Stephen > > > On 18/05/16 12:21, Filippo Cucchetto wrote: > > Hello everyone, > i would like to warn a

[Development] ListView and spaces QTBUG-46488

fix is a no go. Furthermore some knownledge of the internals of QtDeclarative are needed. -- Filippo Cucchetto ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Suggestion: how to know when object is scheduled for deletion

Yep correct 2016-05-06 1:01 GMT+02:00 Thiago Macieira <thiago.macie...@intel.com>: > On quinta-feira, 5 de maio de 2016 22:21:08 PDT Filippo Cucchetto wrote: > > void invokeDeleteLater(QObject* other) { > > other->deleteLater(); > > emit aboutToBeDel

Re: [Development] Suggestion: how to know when object is scheduled for deletion

ay our UI Inventory could be updated to > ignore these objects. > > > > Thanks, > > Sean > > > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > > -

Re: [Development] tarball fetches from code.qt.io?

Maybe https://git-scm.com/docs/git-archive Il 16/mar/2016 19:54, "René J.V." ha scritto: > Hi, > > Is there a way to do tarball fetches from code.qt.io that correspond to a > specific commit, tag or release (for QtWebKit; purely for convenience in a > distribution/packaging

Re: [Development] Qt Coding Guidelines

+1 Il 16/mar/2016 16:14, "Koehne Kai" ha scritto: > Hi there, > > We have had quite some discussions about the use of C++11 features and > right API in the past on this mailing list - but if there has been a > consensus (which is sometimes hard to find out), it was

Re: [Development] debug symbols for official Qt releases

iling list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > +1 -- Filippo Cucchetto ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

[Development] QtQuick mouse event handling

for the click event. Most of the times the user just need to know that an item delegate has been clicked without swallowing it. But for receiving the click event he must swallow (accept) the press event. -- Filippo Cucchetto ___ Development mailing

[Development] Fwd: Making ItemSelectionModel more useful

Hi Alberto, i think that QModelIndex has been brought in for dealing with TreeViews and hierachical item models. To be honest AFAIK you can manipulate QModelIndexes from QML. You can test for validity or obtaining its row or column and model. The implementation should be here

[Development] Linear QQuick layouts change proposal

for the spacing property. For example Layout { spacing: Layout.UniformSpacing } or something like that. In this way we can get the best of both worlds: old behaviour, new behaviour and no dummy items. What do you think? -- Filippo Cucchetto

[Development] QtQuick wrong paint behaviour on window (and maybe other platforms)

seems pretty easy to reproduce them. -- Filippo Cucchetto ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] QML import versions

heir copy of the > application source code, try the app and see if there are any property > > conflicts that needs resolving. Then he can commit that version bump, > possibly together with files to .qml files that resolve conflicts. > > > > > Simon > > > ---

Re: [Development] QML import versions

ossible to implement already in Qt 5, > or is this Qt 6 material? Does someone strongly oppose the idea? How often > do we release new major versions of QML modules? I don't see why QML > modules couldn't follow the same practices than the rest of Qt follows. > Ironically, we've been working on this thing called Qt Quick Controls > 2.0... :P > > > > So what's not possible is the conceptual conflict between arbitrary > > and semantic version numbers. > > Qt, as a whole, uses semantic versioning. I wish that was that only > version number that users had to remember. > > -- > J-P Nurmi > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > -- Filippo Cucchetto ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt Quick Controls Dialogs -- enabled state of the standard buttons (API choices)

I totally agree with the solution proposed by mitch c. With the only exception that i would add a DialogButtonGroup qml element into which put the buttons. This allows us to add functions and logic without clutturing the Dialog component. Furthermore it matches the widget implementation. F. Il

Re: [Development] QtQuick TestCase with other top windows

[mailto:development-bounces+mitch.curtis= theqtcompany@qt-project.org] *On Behalf Of *Filippo Cucchetto *Sent:* Wednesday, 29 July 2015 9:53 PM *To:* development@qt-project.org *Subject:* [Development] QtQuick TestCase with other top windows Hi everyone this is my first post on the mailing list

Re: [Development] QtQuick TestCase with other top windows

yes i'm 2015-07-30 8:49 GMT+02:00 Curtis Mitch mitch.cur...@theqtcompany.com: I thought that you were writing tests within Qt? *From:* Filippo Cucchetto [mailto:filippocucche...@gmail.com] *Sent:* Thursday, 30 July 2015 8:41 AM *To:* Curtis Mitch mitch.cur...@theqtcompany.com *Cc

[Development] QtQuick TestCase with other top windows

would go with the option (1) since i don't want to break everyone's code. -- Filippo Cucchetto ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development