>> This is exactly connect() we already have.
>>
> That's not quite true. First of all, you are not referencing the getter
> in the example above. Then, a ::bind would also initialize the receivers
> value to the current value. Qt::connect does not do that. Also, a ::bind
> suggests that the conne
Hi,Recently I was debugging one of my project and ended up with something which
really surprise me.Are there any special reasons why QVariant compare < not
fully cover appropriate operators from other Qt classes.For example QByteArray
has own operator < but within QVariant switch QByteArray type
Hi Thiago,I am happy ro redesign my code, but how then sorting/filtering models
will work? As data() returns QVariant. Or you plan to use setSorting based on
lambda's and std::function to provide strict types sorting?And what if from API
point of view user want just to specify column without awa
With all respect to Thiago opinion I coldnt agree with it. There is nothing
wrong at all with forwarding comparison of the values with the same data types
to original classes within universal coontainer like QVariant as mentioned in
the previous answer. However I agree that comparing uncomparabl
