QDate, QTime & QDateTime functions

Christian Ehrlicher

@Bracha said in QDate, QTime & QDateTime functions:

Every time I want to change a single item

What's your usecase for this? Creating a QDate/QTime is not that expensive.

Axel Spoerl

In addition to @Christian-Ehrlicher: you can define macros to make your code easier to be read.

Bracha

@Christian-Ehrlicher
Not necessarily expensive as well as cumbersome.
I have some conditions and I need change year/month/day accordingly, and i need to setDate with the parameters that already appear,
like: qDate_tmp.setDate(qDateTime_L.date().year() + 1, qDateTime_L.date().month(),
qDateTime_L.date().day());
qDateTime_L.setDate(qDate_tmp);
instead: qDateTime_L.setYear(qDateTime_L.date().year() + 1)

@Axel-Spoerl
I don't like use Macro's

Christian Ehrlicher

What's wrong with QDate::addYears()?

auto newDate = QDateTime(curDateTime.date().addYear(1), curDateTime.time());
or
curDateTime.setDate(curDateTime.date().addYear(1));

Bracha

@Christian-Ehrlicher
Thank you,
I'll try to play with it and see how it works .
It's still not as simple and bright as the option I suggested but if that's what it is, we'll get it right.
Thank you all.

JonB

@Bracha
Yes it is true that it's a bit awkward to want to e.g. just set one element in an existing QDateTime. It does not help that their are methods on QDate & QTime which help but not on a whole QDateTime. You just have to live with the way Qt does this.

If it were me I would probably write a global "utility" inline function to do a particular operation you want on a QDateTime, for the code you showed.

J.Hilk

@JonB or, hear me out,

you make a new class and inherit from QDateTime where you add those convenient setX functions....

Bracha

@JonB and @J-Hilk
Thank you friends for your understanding and suggestions,
I will seriously consider them and use them.

JonB

@J-Hilk said in QDate, QTime & QDateTime functions:

you make a new class and inherit from QDateTime where you add those convenient setX functions....

But that does not work when existing functions return a QDateTime..... :(

Bracha

@JonB
Will have to convert them to the new object
Another type of awkwardness

J.Hilk

you could, and should, make a constructor that excepts a QDateTime object as argument, that than can be done implicitly :D

Bracha

@Christian-Ehrlicher I actually used your suggestion which is convenient for me at the moment but is probably a solution only for the date and not the time, Just want you to pay attention

Bracha

Just want to summarize the proposed solutions in an orderly fashion so that it remains for the future:

@Christian-Ehrlicher: use QDate::addDays() / QDate::addMonths() / QDate::addYears(). [for dates]
example: [qDateTime.setDate(qDateTime.date().addYears(XXX)]

@JonB : write a global "utility" inline function to do a particular operation you want on a QDateTime.

@J-Hilk: make a new class and inherit from QDateTime where you add those convenient setX functions.
don't forget to convert the returning objects from the existing functions that return a QDateTime object to the new object,
or make a constructor that excepts a QDateTime object as argument, that than can be done implicitly.

Thank you all for a fruitful discussion and varied and helpful suggestions!