On Tue, Apr 28, 2015 at 10:11 PM, Christian Mollekopf
wrote:
> Hey Aleix,
>
>>
>> What about considering the port to be like:
>> QDateTime().time().isNull()?
>>
>> Even QDateTime::isValid documentation mentions that the date and the
>> time need to be valid, therefore the time can be invalid.
>>
>
On Tue, Apr 28, 2015 at 8:47 PM, John Layt wrote:
> On 27 April 2015 at 21:17, Christian Mollekopf wrote:
>
>> 1. add isDateOnly functionality to QDateTime
> ...
>> Opinions following:
>> 1. I'm not sure whether it semantically makes sense to have a QDateTime
>> without a time.
>
> Adding it to Q
On 27 April 2015 at 21:17, Christian Mollekopf wrote:
> 1. add isDateOnly functionality to QDateTime
...
> Opinions following:
> 1. I'm not sure whether it semantically makes sense to have a QDateTime
> without a time.
Adding it to QDateTime was not an option Thiago was happy with so it
didn't m
On Mon, Apr 27, 2015 at 10:17 PM, Christian Mollekopf
wrote:
> Hey,
>
> KDateTime used to have a date-only functionality, that QDateTime is
> lacking. The problem with that is that we need to find a new solution
> for interfaces that allow to set/get either QDate or QDateTime.
>
> One such interfa
Hey,
KDateTime used to have a date-only functionality, that QDateTime is
lacking. The problem with that is that we need to find a new solution
for interfaces that allow to set/get either QDate or QDateTime.
One such interface is KCalCore::Event::start(). For the sake of
discussion getters are mor
