On 27 November 2016 at 16:18, Thiago Macieira wrote:
> On domingo, 27 de novembro de 2016 14:32:20 PST Ch'Gans wrote:
>> Output with KUbuntu 16.10, Qt 5.6:
>> Data changed QVariant(int, 2) Qt::CheckState(Unchecked)
>> Data changed QVariant(int, 0) Qt::CheckState(Unchecked)
>>
>> Output with Offic
On domingo, 27 de novembro de 2016 14:32:20 PST Ch'Gans wrote:
> Output with KUbuntu 16.10, Qt 5.6:
> Data changed QVariant(int, 2) Qt::CheckState(Unchecked)
> Data changed QVariant(int, 0) Qt::CheckState(Unchecked)
>
> Output with Official Qt 5.5 for Linux:
> Data changed QVariant(int, 2) Qt::Che
On 27 November 2016 at 07:59, Thiago Macieira wrote:
> On domingo, 27 de novembro de 2016 00:08:53 PST Ch'Gans wrote:
>> > That explains why _dl_runtime_resolve_avx was used, as opposed to the
>> > non-AVX version of it.
>> >
>> > Note that I can't find that function in glibc's source code. If it
On 27 November 2016 at 14:32, Ch'Gans wrote:
> On 27 November 2016 at 07:40, Thiago Macieira
> wrote:
>> On sábado, 26 de novembro de 2016 21:58:03 PST Ch'Gans wrote:
>>> So my code is build using the same gcc, but behave differently
>>> depending on the qt libraries (qt-5.6-official gives diffe
On 27 November 2016 at 07:40, Thiago Macieira wrote:
> On sábado, 26 de novembro de 2016 21:58:03 PST Ch'Gans wrote:
>> So my code is build using the same gcc, but behave differently
>> depending on the qt libraries (qt-5.6-official gives different result
>> than qt-6.6-ubuntu).
>> And more distur
On sábado, 26 de novembro de 2016 21:58:03 PST Ch'Gans wrote:
> So my code is build using the same gcc, but behave differently
> depending on the qt libraries (qt-5.6-official gives different result
> than qt-6.6-ubuntu).
> And more disturbing, linking against qt-5.5-official gives different
> beha
On domingo, 27 de novembro de 2016 00:08:53 PST Ch'Gans wrote:
> > That explains why _dl_runtime_resolve_avx was used, as opposed to the
> > non-AVX version of it.
> >
> > Note that I can't find that function in glibc's source code. If it really
> > is a problem, then your distribution caused it b
On Saturday 26 November 2016, Ch'Gans wrote:
> So something tells me that, for some reasons, the drop shadow is
> repainted way too many times, yet the app on the screen is updated
> only once every second or so.
>
> Maybe the event loop is going crazy recursive or something like that?
>
Or the s
On Sat, Nov 26, 2016 at 12:08 PM, Ch'Gans wrote:
>
> Maybe the event loop is going crazy recursive or something like that?
I once had a problem like this because I happened to call a function in my
QGraphicsItem::paint(...) that I should not have been calling, such as
moving another item if I r
Hi Alexander, thanks for your reply.
It's not noted in the API but given a `QBluetoothSocket`, I was
wondering what `socketDescriptor` corresponds to and whether I can use
that somehow to obtain the socket pointer that can be used with Bluez'
`bind()`?
In any case, is there planned support f
On 26 November 2016 at 19:55, Thiago Macieira wrote:
> On sábado, 26 de novembro de 2016 13:01:03 PST Ch'Gans wrote:
>> On 26 November 2016 at 11:57, Thiago Macieira
> wrote:
>> > That's a useless result. Your tool is telling you not the proper time of
>> > each function, but the aggregate time o
On 26 November 2016 at 20:02, Thiago Macieira wrote:
> On sábado, 26 de novembro de 2016 15:22:43 PST Ch'Gans wrote:
>> Why is QVariant behaviour changing depending on the compiler version?
>
> You did not test multiple compiler versions. Never once in your email did you
> mention a single GCC ver
12 matches
Mail list logo
