Re: [Interest] Editor history (was: Re: Signal/Slot connection, fails, ...)

2020-02-17 Thread Roland Hughes
On 2/17/20 5:00 AM, interest-requ...@qt-project.org wrote: One of the only two(*) things I miss about using Eclipse is that it automatically kept a history of file changes every time you saved (up to some configurable time period). And a built-in diff viewer where it was easy to compare

[Interest] process setting on QWidget - how

2020-02-17 Thread Sujan Dasmahapatra
QProcess *process = new QProcess(); QStringList progargs; progargs << "/C" << "start C:\\ProgramData\\Microsoft\\Windows\\myapp.exe dicom:get

Re: [Interest] Signal/Slot connection fails, even though QMetaObject::activate is called

2020-02-17 Thread Max Paperno
Hi Matthew, On 2/17/2020 4:27 PM, Matthew Woehlke wrote: On 15/02/2020 00.40, Max Paperno wrote: To me this says that you specifically want the connection to be destroyed when the `context` object goes away, in case the sender and receiver/context objects aren't the same for some reason. The

Re: [Interest] Fwd: Re: Signal/Slot connection fails, even though QMetaObject::activate is called

2020-02-17 Thread Giuseppe D'Angelo via Interest
Il 08/02/20 03:37, Jonathan Purol ha scritto: After manually removing every line of code to see when a MVCE would work, I found a loose `blockSignals(true)` flying around that was there from a debugging session. By the way: there's QSignalBlocker for not forgetting... HTH, -- Giuseppe

Re: [Interest] Signal/Slot connection fails, even though QMetaObject::activate is called

2020-02-17 Thread Matthew Woehlke
On 15/02/2020 00.40, Max Paperno wrote: > On 2/14/2020 11:19 PM, Tony Rietwyk wrote (in part): >> Both overloads have the following warning: > > No they don't... Looking at doc.qt.io for 5.14 anyway. Only the one with > `context` has the part about the context being destroyed (emphasis mine): >

Re: [Interest] Signal/Slot connection fails, even though QMetaObject::activate is called

2020-02-17 Thread Matthew Woehlke
On 16/02/2020 21.33, Max Paperno wrote: > Happened to stumble upon this clazy check while searching on a > completely different issue. > Seems to explain the reasoning pretty well. > > https://github.com/KDE/clazy/blob/master/docs/checks/README-connect-3arg-lambda.md Thanks for sharing the link!

Re: [Interest] QWebSocket text methods should be utf8?

2020-02-17 Thread Konstantin Tokarev
14.02.2020, 23:56, "Thiago Macieira" : > On Friday, 14 February 2020 11:13:24 PST Jason H wrote: >>  After reviewing the QWebSocket spec ( https://tools.ietf.org/html/rfc6455 ) >>  text frames are supposed to be UTF-8 encoded, which would mean that >>  QByteArray would be the proper class. > >

Re: [Interest] QWebSocket text methods should be utf8?

2020-02-17 Thread Giuseppe D'Angelo via Interest
Il 15/02/20 15:46, Roland Hughes ha scritto: The QString class, by virtue of the little yippy-yappy dogs it is running on isn't big-endian hence your continually calling toUtf8(). Endianess has nothing to do with this: 1) QString is UTF-16 encoded (in host byte order). The whole ordeal is

[Interest] Editor history (was: Re: Signal/Slot connection fails, ...)

2020-02-17 Thread Max Paperno
One of the only two(*) things I miss about using Eclipse is that it automatically kept a history of file changes every time you saved (up to some configurable time period). And a built-in diff viewer where it was easy to compare revisions, revert all or parts, etc. Would be great to have that

Re: [Interest] QML property lint suggestion

2020-02-17 Thread Ulf Hermann
> I'm here watching Ulf's QtWS19 QML talk and had a thought... I might > be dumb or crazy (either are equally likely) but, the other day I > added a property called 'data' and completely broke my application. > It was to store data I received. However QML also declares a property > 'data' which is