> On Apr 13, 2016, at 10:06 AM, Hunger Tobias
> wrote:
>
> Hello Qt Developers,
>
> I hereby nominate Marco Benelli for Approver status. He has put in a lot of
> effort to maintain the QML code inside Qt Creator over the recent month and in
months
> fact is the default assignee for all bugs
> On Apr 10, 2016, at 7:22 AM, jaso...@mail-central.com wrote:
>
> Use of Qt Keyboard shortcuts has been broken in Qt for years.
>
> There are lots of bugs about it in Qt and KDE projects.
>
> This one looks close to what I'm seeing,
>
> Can't assign keyboard shortcut with Meta modifiers
> On Mar 16, 2016, at 20:33, André Somers wrote:
>
>
>
> Op 16/03/2016 om 16:14 schreef Koehne Kai:
>> 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 someti
> On Mar 2, 2016, at 11:23 AM, Milian Wolff wrote:
>
> On Mittwoch, 2. März 2016 10:14:18 CET Ziller Eike wrote:
>>> On Feb 29, 2016, at 1:21 PM, Milian Wolff wrote:
>>>
>>> On Friday, February 26, 2016 3:56:08 PM CET Thiago Macieira wrote:
>>>
&g
> On Feb 29, 2016, at 1:21 PM, Milian Wolff wrote:
>
> On Friday, February 26, 2016 3:56:08 PM CET Thiago Macieira wrote:
>> On sexta-feira, 26 de fevereiro de 2016 20:30:28 PST Milian Wolff wrote:
The main problems of templated QObject are captured more or less in
this
thre
> On Feb 20, 2016, at 7:04 PM, Thiago Macieira
> wrote:
>
> On sexta-feira, 19 de fevereiro de 2016 21:01:02 PST Knoll Lars wrote:
>> * We drop support for VS2012. This implicitly drops support for WEC2013.
>> Reason is that the compiler is still having rather large problems with it's
>> C++11
> On Feb 10, 2016, at 6:36 PM, Petroules Jake
> wrote:
>
>
>> On Feb 10, 2016, at 8:11 AM, Tor Arne Vestbø
>> wrote:
>>
>> On 10/02/16 17:06, Thiago Macieira wrote:
>>> On quarta-feira, 10 de fevereiro de 2016 12:00:00 PST Tor Arne Vestbø wrote:
Does anyone see any issues with this goi
> On Jan 23, 2016, at 1:12 AM, Kevin Kofler wrote:
>
> Ziller Eike wrote:
>>> I would like that trend to continue. The likely next candidates are
>>> threads, futures and locks.
>>
>> +1
>
> I wonder why everyone so far agreed on that. So let me
> On Jan 23, 2016, at 1:47 AM, Thiago Macieira
> wrote:
>
> On Saturday 23 January 2016 01:23:30 Kevin Kofler wrote:
>> I feel it's actually TOO rapidly changing. C++11 even threw out C
>> compatibility, not only by not adopting all C99 improvements (e.g. VLAs),
>> but also by subtly interpreti
> On Jan 20, 2016, at 3:12 PM, Marc Mutz wrote:
>
> On Wednesday 20 January 2016 11:48:20 Bubke Marco wrote:
>> I think it would be productive for the discussion to build story of what we
>> want to do. A story of the big picture. Maybe as a first step we can show
>> how we tackle problems with
> On Jan 19, 2016, at 10:40 PM, Marc Mutz wrote:
>
> On Tuesday 19 January 2016 19:56:38 Mathias Hasselmann wrote:
>> Am 19.01.2016 um 15:21 schrieb Ziller Eike:
>>>> On Jan 19, 2016, at 16:09, Marc Mutz wrote:
>>>> I doubt many people actively use the fa
> On Jan 19, 2016, at 16:09, Marc Mutz wrote:
>
> On Tuesday 19 January 2016 14:33:46 Giuseppe D'Angelo wrote:
>> On Tue, Jan 19, 2016 at 3:07 PM, Marc Mutz wrote:
>>> I'd aggregate the std container instead of inheriting it, but yes, that's
>>> a good idea. I just wrote a mail suggesting essen
> On Jan 7, 2016, at 10:14 PM, René J. V. Bertin wrote:
>
> Sorvig Morten wrote:
>
>> Another point: Isn't there a fundamental incompatibiity between
>> LaunchServices
>> and QProcess? LanchServices may ‘activate’ an already running process, while
>> QProcess always starts a new process.
That
> On Dec 22, 2015, at 1:28 PM, Marc Mutz wrote:
>
> On Tuesday 22 December 2015 11:26:40 Ziller Eike wrote:
>> We have something similar in Qt:
>>
>>QString a = "ABC";
>>QString b = "abc";
>>auto result = a + b;
>>
> On Dec 8, 2015, at 10:46 AM, Ziller Eike wrote:
>
>
>> On Dec 7, 2015, at 2:41 PM, Knoll Lars wrote:
>>
>> On 07/12/15 15:44, "Development on behalf of Marc Mutz"
>> wrote:
>>
>>
>>
>>> On Monday 07 December 2015 13
> On Dec 12, 2015, at 10:22 AM, anton wrote:
>
> Hi,
>
> just tested the visualstudio 2015 version on windows.
> One thing I noticed:
>
> In the Designer of a Qt Widgets Application,
> the QWebView Widget is missing.
>
> Are you aware of this?
Since QtWebKit is deprecated and no binaries are
> On Dec 7, 2015, at 2:41 PM, Knoll Lars wrote:
>
> On 07/12/15 15:44, "Development on behalf of Marc Mutz"
> wrote:
>
>
>
>> On Monday 07 December 2015 13:48:58 Ziller Eike wrote:
>>> I do not think that more usage of ‘auto’ will make any code
> On Dec 4, 2015, at 8:01 PM, Olivier Goffart wrote:
>
> On Friday 4. December 2015 15:39:01 Curtis Mitch wrote:
>>> -Original Message-
>>> From: Development [mailto:development-boun...@qt-project.org] On Behalf Of
>>> Olivier Goffart
>>> Sent: Friday, 4 December 2015 2:25 PM
>>> To: dev
> On Dec 4, 2015, at 00:05, Benjamin TERRIER wrote:
>
> Hi everyone,
>
> This message follows an exchange I've had with Thiago on a bug report:
>https://bugreports.qt.io/browse/QTBUG-49749
>
>
> In the current state, QMetaObject::connectSlotsByName() tries to find,
> for each slot named "
> On Oct 28, 2015, at 3:09 PM, Gil Moses wrote:
>
> Hi,
>
> I've built Mac universal binaries of v5.5.1 (built separately for i386 and
> x86_64, then used lipo).
> Built and ran my Qt app (Xcode 5, Mavericks), and got this error:
>
> . could not find or load the Qt platform plugin "cocoa".
>
> On Oct 16, 2015, at 9:10 AM, Poenitz Andre
> wrote:
>
>
> Marc Mutz wrote:
>>> I think too we should embrace the standard library more and don't replicate
>>> their features.
>>
>> So you think that QStringView is too experimental and _at the same time_
>> replicating the standard. Sounds p
> On Oct 14, 2015, at 5:14 PM, Matthew Woehlke wrote:
>
> On 2015-10-14 10:30, André Somers wrote:
>> Op 14-10-2015 om 15:59 schreef Matthew Woehlke:
>>> STL should change. In Qt and Python, you can use negative indices to
>>> refer to a distance (length) relative to the end (length) of the stri
> On Sep 29, 2015, at 8:40 PM, Oswald Buddenhagen
> wrote:
>
> On Tue, Sep 29, 2015 at 08:32:21AM -0700, Jake Petroules wrote:
>> If you set QMAKE_RPATHDIR to some value (including an empty value),
>> then qmake won't add the absolute path in the first place.
>>
> note that things are differen
> On Sep 29, 2015, at 10:16, Jake Petroules
> wrote:
>
>
>> On Sep 28, 2015, at 2:30 PM, Massimo Callegari
>> wrote:
>>
>> On Monday 28 September 2015 19:09:11 Massimo Callegari wrote:
But please guys, when introducing such an important change, you are
warmthly
invited to me
> On Sep 29, 2015, at 10:27, Jake Petroules
> wrote:
>
>
>> On Sep 28, 2015, at 2:40 PM, Thiago Macieira
>> wrote:
>>
>> On Monday 28 September 2015 21:30:33 Massimo Callegari wrote:
Can you explain what broke for you?
>>>
>>> Since Qt 4.8 and up to Qt 5.4.2 I was using the install_na
> On Aug 18, 2015, at 08:49, Thiago Macieira wrote:
>
> On Monday 17 August 2015 23:25:05 Jake Petroules wrote:
>> I haven't a clue why people would bother using old OS X platforms for
>> development, *especially* now that they don't charge for it. Plus I think
>> submitting to app stores requir
> On Jun 16, 2015, at 16:52, Matthew Woehlke
> wrote:
>
> On 2015-06-12 17:45, Thiago Macieira wrote:
>> On Friday 12 June 2015 10:49:38 Matthew Woehlke wrote:
On Friday 12 June 2015 08:08:51 André Somers wrote:
> Not available for use are:
> * = default,
> * = deleted,
>>>
>>
> On May 23, 2015, at 05:03, Ariel Molina wrote:
>
> Hi,
>
> I solved the problem, just want to share,
>
> On Wed, May 20, 2015 at 12:16 PM, Edward Sutton
> wrote:
> I understand the config commands used to build Qt packages are here:
>
> http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packagi
> On May 10, 2015, at 9:08 PM, mark diener wrote:
>
> Well, it looks like the big weakness in OSX deployment is macdeployqt and we
> are on version 5.4.1+
>
> I was able to change my macdeployqt command line FROM:
>
> macdeployqt ./testdep.app/ -qmldir=/macdev/qdev/testdep/ -verbose=2
>
>
> On Apr 21, 2015, at 11:46 AM, René J.V. Bertin wrote:
>
> Hi,
>
> I know I should ask this on the QC ML (but I'd prefer not to sign up for just
> an occasional question like this):
>
> Is there a (good) reason why DocumentManagerPrivate::linkWatcher() forces the
> use of a polling watcher?
> On Mar 21, 2015, at 7:40 PM, Thiago Macieira
> wrote:
>
> We'd like to make Qt build unconditionally with the latest version of the C++
> standard that is supported by the compiler. That implies removing the -c++11
> option so that the -no-c++11 option goes away too.
>
> Possible drawbacks
> On Feb 20, 2015, at 10:04 AM, André Somers wrote:
>
> Bo Thorsen schreef op 20-2-2015 om 09:03:
>> Andrés question about how this would change the API is a lot more
>> interesting. I so far haven't seen a single case where someone has
>> described how access to lambdas might improve the API.
> On Feb 10, 2015, at 10:51 AM, Marc Mutz wrote:
>
> On Tuesday 10 February 2015 08:41:47 Ziller Eike wrote:
>>> On Feb 9, 2015, at 3:40 PM, Marc Mutz wrote:
>>>
>>> On Monday 09 February 2015 09:54:12 Smith Martin wrote:
>>>> This is the kind
> On Feb 9, 2015, at 3:40 PM, Marc Mutz wrote:
>
> On Monday 09 February 2015 09:54:12 Smith Martin wrote:
>> This is the kind of thing we should add to the documentation, but can you
>> elaborate? I mean, illustrate the meaning of "locality of reference,"
>> "wildly mixing insertions, lookups,
> On Feb 6, 2015, at 09:21, Simon Hausmann
> wrote:
>
> On Friday 6. February 2015 08.42.53 André Somers wrote:
>> Knoll Lars schreef op 5-2-2015 om 16:28:
>>> But we don’t have much of a choice, if we want to deliver an up to date
>>> web engine.
>>
>> Perhaps it is time to ask the question t
> On Feb 3, 2015, at 8:33 AM, Knoll Lars wrote:
>
> Hi,
>
> I’d like to mark a few modules as deprecated with 5.5, and most likely
> remove them from the binary packages with 5.6. These modules are:
>
> * Qt WebKit
As long as WebEngine is not (yet?) a “full" replacement of Qt WebKit
function
> On Jan 18, 2015, at 6:34 AM, Kevin Kofler wrote:
>
> Thiago Macieira wrote:
>> Now we have a legacy to keep, so we can't accept a radical change. Only
>> incremental improvements.
>
> You will find that very few deployments out there in the real world use
> qtchooser. The widely-used RHEL mo
> On Jan 18, 2015, at 10:24 PM, Kevin Kofler wrote:
>
> Konstantin Ritt wrote:
>> There is no need for moc/rcc/uic to be suffixed. In fact, they are an
>> internal build tools invoked by qmake and thus they should normally reside
>> in libexec dir (or you may query qmake for its specific libexec
> On Jan 9, 2015, at 10:10 PM, Thiago Macieira
> wrote:
>
> On Friday 09 January 2015 20:19:36 André Pönitz wrote:
>> In some case these macros even expand to something else than the "obviously
>> related" C++ keyword, so potential benefits gained from using the actual
>> feature have to be wei
On Oct 17, 2014, at 7:26 PM, Mathias Hasselmann
wrote:
>
>
> Am 17.10.2014 um 18:31 schrieb Thiago Macieira:
>> On Friday 17 October 2014 13:06:39 Milian Wolff wrote:
>>> enum Foo {
>>> Bar = 1, Baz = 2
>>> };
>>>
>>> Foo foo = static_cast(3);
>>>
>>> Now what do you do without a default cl
On Oct 13, 2014, at 5:23 PM, Matt Broadstone wrote:
> On Mon, Oct 13, 2014 at 11:07 AM, Ziller Eike
> wrote:
>>
>> On Oct 13, 2014, at 4:55 PM, Matt Broadstone wrote:
>>
>>> Hi all,
>>>
>>> I've been using qt 4.8.6 for quite som
On Oct 13, 2014, at 4:55 PM, Matt Broadstone wrote:
> Hi all,
>
> I've been using qt 4.8.6 for quite some time on my macbook installed
> from homebrew with no problem whatsoever. I decided over the weekend
> to upgrade my install to the latest qt5 build which on homebrew is
> 5.3.2. Everything
On Oct 13, 2014, at 10:30 AM, Morten Johan Sørvig
wrote:
>
>> On 10 Oct 2014, at 13:27, Ziller Eike wrote:
>>
>>
>> On Oct 10, 2014, at 11:48 AM, Morten Johan Sørvig
>> wrote:
>>
>>>>
>>>>> Mac people: do we need access
On Oct 10, 2014, at 8:16 PM, Adam Light wrote:
>
>
> On Fri, Oct 10, 2014 at 7:25 AM, Ziller Eike
> wrote:
>
> On Oct 10, 2014, at 3:37 PM, Adam Light wrote:
>
> > On the flip side, our large Qt application runs on Mac and Windows and
> > we're
On Oct 10, 2014, at 3:37 PM, Adam Light wrote:
>> On Fri, Oct 10, 2014 at 4:27 AM, Ziller Eike
>> wrote:
>>
>> On Oct 10, 2014, at 11:48 AM, Morten Johan Sørvig
>> wrote:
>>
>> >>
>> >>> Mac people: do we need access to p
On Oct 10, 2014, at 11:48 AM, Morten Johan Sørvig
wrote:
>>
>>> Mac people: do we need access to plist files?
>>
>> Plist is the format for application and other settings on OS X, and there
>> are native tools for nicely editing these. Ini is highly alien on OS X.
>> So, I’d answer yes.
>
>
On Oct 10, 2014, at 12:48 AM, Thiago Macieira wrote:
> On Thursday 09 October 2014 19:43:08 Tomaz Canabrava wrote:
>> Please be kind, this is the first step to contributing to qt that I'm
>> trying. :)
>>
>> First, I'v implemented the rationale that thiago asked me to do on the
>> other thread:
On Oct 8, 2014, at 1:36 PM, Thiago A. Corrêa wrote:
> Hi,
>
> On Wed, Oct 8, 2014 at 5:10 AM, Ziller Eike
> wrote:
>>
>> QIcon does automatic loading of @2x images afair. QPixmap and QImage only
>> set the devicePixelRatio corresponding to the file name auto
On Oct 8, 2014, at 9:18 AM, Robert Iakobashvili wrote:
> On Wed, Oct 8, 2014 at 10:03 AM, Ziller Eike
> wrote:
>>
>> On Oct 6, 2014, at 1:59 PM, Robert Iakobashvili wrote:
>>
>>> Gentlemen,
>>> If images are placed to resource file,
>>> is
On Oct 7, 2014, at 8:43 AM, Robert Iakobashvili wrote:
> On Mon, Sep 22, 2014 at 1:03 PM, Sorvig Morten
> wrote:
>>
>>> On 19 Sep 2014, at 11:28, Sorvig Morten wrote:
>>>
>>> This will indeed receive attention in the coming days. There are already
>>> some patches attached to the QTBUGs. I
On Oct 6, 2014, at 1:59 PM, Robert Iakobashvili wrote:
> Gentlemen,
> If images are placed to resource file,
> is there any option for an automatic management
> of using either Retina or non-Retina images
> using Apple's naming convention or the manual
> management is the only option like for Ma
Just for completeness ;)
https://bugreports.qt-project.org/browse/QTBUG-27728
On Sep 28, 2014, at 9:52 AM, Samuel Gaist wrote:
>
>> On 28 sept. 2014, at 03:26, Thiago Macieira
>> wrote:
>>
>>> On Sunday 28 September 2014 01:02:11 Samuel Gaist wrote:
>>> Hi,
>>>
>>> Following a post on the
On Sep 25, 2014, at 4:07 PM,
wrote:
>
>> I think if this feature would be added to QtCore, it should be by extending
>> QMetaObject::invoke to work with functors.
>> By using Qt::BlockingQueuedConnection that would be very similar to what you
>> have done.
>
> I reported this before in Qt is
This was cross-posted :/
My answer will possibly not end up on the interest mailing list.
On Sep 2, 2014, at 10:31 AM, Ziller Eike wrote:
>
> On Sep 2, 2014, at 9:01 AM, Rutledge Shawn wrote:
>
>>
>> On 1 Sep 2014, at 8:32 PM, Thiago Macieira wrote:
>>
>>&g
On Sep 2, 2014, at 9:01 AM, Rutledge Shawn wrote:
>
> On 1 Sep 2014, at 8:32 PM, Thiago Macieira wrote:
>
>> On Monday 01 September 2014 12:50:23 Graham Labdon wrote:
>>> Hi
>>> My application is internationalized, however, in some circumstances I need
>>> the English version of the string no
On Aug 26, 2014, at 4:02 AM, quinn.wj.xie wrote:
>
> Hello, everyone at development@qt-project
>
> I have a question and want some suggestions. Right now I am learning Qt
> programming. And I was wondering if Qt supports a customed web browser.
> Because our lab is working on a new Interne
On Aug 25, 2014, at 3:09 AM, Jake Petroules
wrote:
> `export DYLD_IMAGE_SUFFIX=_debug` before running your application. Simple as
> that. Note that this option will be ignored if DYLD_ROOT_PATH is set.
>
> See
> https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/
On Aug 21, 2014, at 5:16 PM, Marc Mutz wrote:
> On Thursday 21 August 2014 16:52:05 Thiago Macieira wrote:
>> But I'd like QOptional o = QString() result in a null
>> (disengaged) QOptional too.
Why would that be?
The optional got a QString value assigned. It shouldn’t care about more.
> Too
On Aug 13, 2014, at 5:07 PM, Daniel Teske wrote:
> On Wednesday 13 Aug 2014 08:05:52 Thiago Macieira wrote:
>> On Wednesday 13 August 2014 14:32:13 Ziller Eike wrote:
>>> So my question: Does anyone have any idea how this could possibly happen,
>>> how we could reprod
For Qt Creator we get the following crash reported:
https://bugreports.qt-project.org/browse/QTCREATORBUG-11262
It seems to happen randomly, on unix (i.e. OS X and Linux) but possibly not on
Windows, at least Qt 5.2.1 and later, and the seemingly only person in the
Berlin office which also gets
On Aug 13, 2014, at 12:32 PM, Adam Strzelecki wrote:
> Ziller Eike wrote:
>
>> Can we please already now turn a cross-platform hat on, and at least think
>> about options that at least do not right away block using the same for
>> non-OS X?
>
> Sure, this is
On Aug 13, 2014, at 11:07 AM, Oswald Buddenhagen
wrote:
> On Tue, Aug 12, 2014 at 07:08:45PM -0400, Jake Petroules wrote:
>> On 2014-08-12, at 06:50 PM, Adam Strzelecki wrote:
>>> I agree that such facility should be provided internally while
>>> implementing Phase II changes.
>>>
(1) Ad
On Aug 12, 2014, at 9:14 PM, Jake Petroules
wrote:
> On 2014-08-12, at 12:36 PM, Adam Strzelecki wrote:
>
>>> Default behavior: I’m on favor of keeping it opt-in, either via "CONFIG +=
>>> bundle_frameworks" or “make bundle”
>>
>> Me too. However as I said previously stakeholders are to dec
On Aug 12, 2014, at 4:25 PM, Adam Strzelecki wrote:
> Okay, Phase II.
>
> (1) Introduce "bundle_frameworks" CONFIG option, and set it default for
> "rpath" shared builds on iOS & OS X
Can we please already now turn a cross-platform hat on, and at least think
about options that at least do no
On Aug 12, 2014, at 1:37 PM, Adam Strzelecki wrote:
>> On to my now standard question: Can you summarize the discussion so far into
>> a proposal on what you want to change? Keep it as short as possible :) For
>> example, I think it’s understood that (incremental) framework coping is fast
>>
On Aug 11, 2014, at 11:15 PM, Jake Petroules
wrote:
> On 2014-08-11, at 10:42 AM, Ziller Eike wrote:
>
>>>>
>>>>> In a terminal session, simply:
>>>>>
>>>>> $ export DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:/path/to/Qt/Frameworks
&
On Aug 3, 2014, at 12:39 AM, Jake Petroules
wrote:
> On 2014-08-02, at 05:04 AM, Adam Strzelecki wrote:
>
>>> Please don't exaggerate the performance implications of copying a few
>>> frameworks on the first build (…)
>>
>> This can be done, but discussion is going off-topic.
>>
>> Let us
On Jul 17, 2014, at 3:14 PM, Ziller Eike wrote:
>
> On Jul 17, 2014, at 1:28 PM, Jędrzej Nowacki
> wrote:
>
>> On Thursday 17 of July 2014 10:51:03 you wrote:
>>> QVariant::operator== is not symmetric
>>>
>>>QDateTime dateTime = Q
On Jul 17, 2014, at 1:28 PM, Jędrzej Nowacki wrote:
> On Thursday 17 of July 2014 10:51:03 you wrote:
>> QVariant::operator== is not symmetric
>>
>> QDateTime dateTime = QDateTime::currentDateTime();
>>QTime time = dateTime.time();
>>
>>qDebug() << (QVariant(dateTime) == QVariant(t
On Jul 17, 2014, at 2:38 PM, Jędrzej Nowacki wrote:
> On Thursday 17 of July 2014 13:33:49 Daniel Teske wrote:
>> On Thursday 17 Jul 2014 13:28:10 Jędrzej Nowacki wrote:
>>> On Thursday 17 of July 2014 10:51:03 you wrote:
QVariant::operator== is not symmetric
QDateTime dateTi
On Jul 16, 2014, at 1:45 PM, Poenitz Andre wrote:
> Olivier Goffart wrote:
>> Jędrzej Nowacki wrote:
>> [...]
What is wrong with string -> int or bytearray -> int?
>>>
>>> At the very least, _implicit_ conversions should not lose data,
>>> i.e. a A a1; B b = a1; A a2 = b; round trip idea
On Jul 16, 2014, at 5:04 PM, Thiago Macieira wrote:
> On Wednesday 16 July 2014 15:01:53 Ziller Eike wrote:
>> No idea what happens in animations, but I’d suppose that any conversions
>> there would be accidentally.
>
> QPropertyAnimation is based on modifying QVariants,
On Jul 16, 2014, at 4:03 PM, Sze Howe Koh wrote:
> On 7 July 2014 19:11, Frederik Gladhorn wrote:
>> Mandag 7. juli 2014 10.02.55 skrev Ziller Eike:
>>> On Jul 7, 2014, at 11:17 AM, Frederik Gladhorn
>> wrote:
>>>> Mandag 7. juli 2014 07.10.00 skrev Koehn
On Jul 16, 2014, at 1:30 PM, Jędrzej Nowacki wrote:
> On Wednesday 16 of July 2014 06:37:25 Ziller Eike wrote:
>> I don’t think we have a single place in Qt Creator where we want automatic
>> conversions when using QVariant. A search for QVariant(Map) returns 5400
>> hits
On Jul 16, 2014, at 11:58 AM, Konrad Rosenbaum wrote:
> On Wednesday 16 July 2014 08:41:07 Poenitz Andre wrote:
>> Olivier Goffart wrote:
>>> It's always a dilemma. We have to look at how likely we are to break
>>> applications and I don't think adding a conversion is likely to cause
>>> breakag
On Jul 16, 2014, at 11:28 AM, Jędrzej Nowacki wrote:
> On Wednesday 16 of July 2014 06:37:25 Ziller Eike wrote:
>> [...]
>>> When one use QVariant, it is because we want to enjoy dynamic typing and
>>> nice conversions.
>>
>>
>> I don’t think
On Jul 15, 2014, at 7:36 PM, Olivier Goffart wrote:
> On Tuesday 15 July 2014 10:38:52 Poenitz Andre wrote:
>> Olivier Goffart wrote:
>>> Jędrzej Nowacki wrote:
1. Are we allowed to add new conversions?
The question is tricky because adding a new conversion is a
beh
On Jul 14, 2014, at 1:46 PM, steveg2...@gmail.com wrote:
> This is from the Application Output widow
Have a look at your run configuration in projects mode then, because it looks
like you are running mingw32-make.exe when pressing “run” in Qt Creator,
instead of your application.
(http://qt-pr
On Jul 11, 2014, at 6:21 AM, Christian Gagneraud wrote:
> On 11/07/2014 11:22 a.m., Thiago Macieira wrote:
>> On Friday 11 July 2014 10:05:03 Christian Gagneraud wrote:
>>> Boot To Qt for Embedded Linux (Not talking about android here), is based
>>> on Yocto (which is open-source), there exists
On Jul 7, 2014, at 11:17 AM, Frederik Gladhorn
wrote:
> Mandag 7. juli 2014 07.10.00 skrev Koehne Kai:
>>> -Original Message-
>>> From: development-bounces+kai.koehne=digia@qt-project.org
>>> [...]
>>> 1) Developers who face regressions (not just testers) are now in an
>>> awkward
>
On Jul 6, 2014, at 3:52 AM, Sze Howe Koh wrote:
> On 4 July 2014 00:14, Thiago Macieira wrote:
>> On Thursday 03 July 2014 10:35:30 Koehne Kai wrote:
>>> Right, the files are still there. But to allow parallel installation (which
>>> is probably what you want if you e.g. are after regression te
On Jun 20, 2014, at 8:53 AM, Rutledge Shawn wrote:
>
> On 20 Jun 2014, at 08:32, Knoll Lars wrote:
>
>> Hi,
>>
>> Currently Qt WebKit and Qt WebKit Widgets are marked in our documentation
>> as Qt Essentials. I’d like to propose to move them to the add-on category
>> for 5.4.
>>
>> There ar
On Jun 12, 2014, at 6:51 PM, Oswald Buddenhagen
wrote:
> On Thu, Jun 12, 2014 at 04:08:17PM +0200, Aurélien Gâteau wrote:
>> Olivier Goffart wrote:
>>> But just wondering if it would not be better to have that as an API within
>>> QGridLayout such as
>>> QGridLayout::setAlignedWith(QGridLayout
On May 23, 2014, at 6:03 PM, m...@rpzdesign.com wrote:
> Sorvig:
>
>> From the latest new front:
>
> http://bgr.com/2014/03/18/nexus-9-specs-details/
>
> Digitimes on Tuesday cited its own research arm in reporting that Google
> will launch two new Nexus tablets in 2014. In addition to an upda
On Apr 28, 2014, at 8:12 PM, Alan Alpert <4163654...@gmail.com> wrote:
> On Mon, Apr 28, 2014 at 7:36 AM, Sze Howe Koh wrote:
>> On 25 April 2014 18:18, Joerg Bornemann wrote:
>>> On 25-Apr-14 04:21, Sze Howe Koh wrote:
>>>
I consider QML and JavaScript to be different languages. JavaScri
On Apr 7, 2014, at 12:26 PM, Amit Biran wrote:
> Hello,
>
> I'm trying to build on MacOS any of the Example Qt projects.
>
> OSX:
>10.8.5 (Mountain Lion)
> Qt Creator Info:
>Based on Qt 5.2.1 (Clang 5.0 (Apple), 64 bit)
>Built on Jan 31 2014 at 06:00:56
> Xcode Info:
>Ve
On Apr 4, 2014, at 10:51 AM, Tomasz Siekierda wrote:
> On 3 April 2014 10:47, List for announcements regarding Qt releases
> and development wrote:
>> We are happy to announce the Qt Creator 3.1 RC1 release
>>
>> Blog: http://blog.qt.digia.com/blog/2014/04/03/qt-creator-3-1-rc1-released/
>> Do
On Feb 25, 2014, at 6:40 PM, Thiago Macieira wrote:
> Em ter 25 fev 2014, às 11:33:00, Oswald Buddenhagen escreveu:
>>> I.e., nothing changes. I propose this branch stay named "dev", for clarity
>>> of purpose, not "master".
>>
>> i don't think the clarity buys us much. like the rest of the bra
On Jan 26, 2014, at 8:10 PM, Robert Knight wrote:
>> In regards to users of Mac OS Qt applications: I’m am extremely confident
>> that more Mac OS applications would be/have been written in Qt,
>> if the priority for native looking widget support was higher. Mac OS users
>> are notorious for t
On Jan 23, 2014, at 7:16 PM, Adam Light wrote:
> All but one developer at my (smallish) company is still using OSX 10.6.8
> because we need 10.6 to be able to build the current shipping version of our
> main product. We all use Qt Creator, so a Creator 3.2 that would not work on
> 10.6 would
On Jan 22, 2014, at 8:31 PM, Cristian Adam wrote:
> On 22.01.2014 19:35, ext Olivier Goffart wrote:
>> Regarding the use of libclang for the code model in Qt creator, there
>> was no progress in a long time.
>
> I think the clang code model branch has been merged into master:
> http://lists.q
On Jan 21, 2014, at 2:56 PM, Tor Arne Vestbø wrote:
> On 21/01/14 13:36 , Sorvig Morten wrote:
>> I realize that if I’m the only one who want’s to keep supporting 10.6
>> then that’s not going to work. The most important thing to me is to
>> have a somewhat predictable deprecation plan. For exam
On Jan 21, 2014, at 3:15 PM, Sorvig Morten wrote:
> On 20 Jan 2014, at 21:21, deDietrich Gabriel
> wrote:
>> The truth is, market share doesn’t mean anything. Point in case: According
>> to the link above, OS X is less than 8% of the total market share. Should we
>> then drop the Mac port co
On Jan 21, 2014, at 3:01 PM, Mohamed Fawzi wrote:
>
> On 21 Jan 2014, at 14:25, Jake Petroules
> wrote:
>
>> On Jan 21, 2014, at 7:36 AM, Sorvig Morten wrote:
>>
>>> On 21 Jan 2014, at 11:51, Simon Hausmann wrote:
>>>
>>> That depends on how much time we spend releasing Qt :)
>>>
>>> I
On Jan 11, 2014, at 5:55 AM, Kuba Ober wrote:
> On Jan 10, 2014, at 6:07 AM, Ziller Eike wrote:
>
>> On Jan 9, 2014, at 6:05 PM, Kuba Ober wrote:
>>
>>> I’m trying to figure out the most constructive way of ensuring that an OS X
>>> build of Qt, in
On Jan 9, 2014, at 6:05 PM, Kuba Ober wrote:
> I’m trying to figure out the most constructive way of ensuring that an OS X
> build of Qt, installed with the source code, can be actually debugged by
> stepping into the C++ source code in the Qt library. So far I can only step
> into disassembl
On Jan 6, 2014, at 11:38 AM, Marc Mutz wrote:
> On Thursday 02 January 2014 21:04:27 Jiergir Ogoerg wrote:
>> buffer() // getter
>> buffer_set(..) // setter
>> BufferSupportsFind() // bool
>>
>> selection() // getter
>> SelectionMove(..) // move selection
>> selection_set(..) // setter
>> Selec
On Dec 18, 2013, at 5:35 PM, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Hi! I would like to now if it's acceptable for the project to have 3rd party
> code with the following statement in 3rd party sources:
>
> "The Software shall be used for Good, not Evil”
Does it come with definitions o
On Dec 11, 2013, at 11:57 AM, Jonathan Liu wrote:
> On 11/12/2013 8:03 PM, Ziller Eike wrote:
>> On Dec 11, 2013, at 6:27 AM, Jonathan Liu wrote:
>>
>>> On 10 December 2013 18:34, Koehne Kai wrote:
>>>>> -Original Message-
>>>>
On Dec 11, 2013, at 6:27 AM, Jonathan Liu wrote:
> On 10 December 2013 18:34, Koehne Kai wrote:
>>
>>> -Original Message-
>>> From: development-bounces+kai.koehne=digia@qt-project.org
>>> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On
>>> Behalf Of Thiago Macie
1 - 100 of 162 matches
Mail list logo
