Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Native Development

Thank you for visiting the BlackBerry Support Community Forums.

BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)

BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.

"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."

- Kevin Michaluk, Founder, CrackBerry.com

Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.

Posts: 76
Registered: ‎02-08-2013
My Device: z10
My Carrier: rogers
Accepted Solution

DateTimePicker Confused about Epoch?

Something quite unusual is happening, it looks like the DateTimePicker in my app suddenly decided that epoch was three days later than it should be:


schedTimePicker = new DateTimePicker();


connect(schedTimePicker, SIGNAL(valueChanged(QDateTime)), this, SLOT(onSchedTimeValueChanged(QDateTime)));


In the slot I have:

void MainClass:: onSchedTimeValueChanged(QDateTime time)


    fprintf(stderr, "%s:%d time=%s\n", __FUNCTION__, __LINE__, time.toString().toUtf8().constData());



When I set the time picker to 00:00:00 the output on the console is:

onSchedTimeValueChanged:5448 time=Sat Jan 3 00:00:00 1970


A full three days after actual epoch. Am I losing it? What's going on?



Posts: 76
Registered: ‎02-08-2013
My Device: z10
My Carrier: rogers

Re: DateTimePicker Confused about Epoch?

Apparently the parameter provided for the valueChanged slot is not what the documentation says it is.


The most reliable way of determining what the value changed _to_ when the slot is called is to look at the picker->value() value instead. I'm suspecting the parameter had the value that was previously set, or something along those lines.