LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why picktime doesn't inherit Timestamp control format?

In LabVIEW 2010 I put the format %<%d/%m/%Y %H:%M:%S>T in Timestamp Control.

 

When user click on the button open picktime object.

 

Why picktime window doesn't inherit format from Timestamp Control and display milliseconds?

Where I can set picktime format?

 

Thanks all

0 Kudos
Message 1 of 8
(3,469 Views)

What is a picktime object / window? 

0 Kudos
Message 2 of 8
(3,449 Views)

I mean the window that appear when you click on button near the timestamp control with title 'Set Time and Date', see attachment.

0 Kudos
Message 3 of 8
(3,445 Views)

I don't see the problem you are seeing.

 

However, I am located in the USA and my Windows 7 PC's system locale setting is probably different from yours.

 

 

0 Kudos
Message 4 of 8
(3,430 Views)

I'm located in Italy and I work with windows XP

 

Thanks, don't'  worry is just a little problem.

0 Kudos
Message 5 of 8
(3,424 Views)

The little window that pops up is actually a separate VI. The way that VI is written, it does not look at the format of the time control to format the text that is written to the string control on the front panel. It uses a default format, which matches the default format of the time control. However, if you change the format of the time control, the format in the popup VI is not changed.

 

If you want this changed you'd have to create your own popup VI and place your own button next to the time control that when clicked opens your popup VI.

 

Or, you can post an idea in the LabVIEW Idea Exchange.

0 Kudos
Message 6 of 8
(3,397 Views)

I went in and changed the default format to the OP's and the pop-up window did reflect that change. I just didn't see the problem he/she had.

 

 

0 Kudos
Message 7 of 8
(3,393 Views)

@nyc_(is_out_of_here) wrote:

I went in and changed the default format to the OP's and the pop-up window did reflect that change. I just didn't see the problem he/she had.


Interesting, as it appears this is something that was fixed (to a certain extent) somewhere along the way. I verified the incorrect behavior with an earlier version of LabVIEW, and I've known this problem to be there forever.

0 Kudos
Message 8 of 8
(3,391 Views)