CurrentDate() & CurrentTime()

Blitz3D Forums/Blitz3D Beginners Area/CurrentDate() & CurrentTime()

_PJ_(Posted 2009) [#1]
The strings returned by these functions do not seem to match the settings in my registry as per Regional Settings.
This hints to me that they are fixed return formats determined within Bllitz, and therefore, regardless of the user or OS< they should always return the same format.

I really hope this is the case as it will make the information a good deal simpler and better than millisecs() for less accurate, longer interval requirements.

Can anyone tell me if they know or experience any different?

Here's what I get:

CurrentDate() = "dd Mmm yyyy"
CurrentTime() = "HH:mm:ss"



stanrol(Posted 2010) [#2]
they do for me with reg. settings.
same format here.
Print CurrentDate$()
Print CurrentTime$()
WaitKey



xtremegamr(Posted 2010) [#3]
CurrentDate/Time() return the right values for me.

P.S. By "regional settings", I assume you mean "the timezone is correct" :P


_PJ_(Posted 2010) [#4]

By "regional settings", I assume you mean "the timezone is correct" :P


My question was not about values, but the format.
The values will always match whatebver the windows system clock is set to. Try changing it in windows to see the difference.

However, my post was referring to the following:
My short Date format is set to "d/m/yy" And long date format is "Dddd, d Mmmm,yyyy" within Windows.

Regardless of this setting, Using Blitz' date function ALWAYS returns "dd Mmm yyyy"


I just wanted to be sure this was equivalent on all versions of windows, not at all affected by changing any windows date-related formatting settings.

However, since I originally posted, I did notice this in the Help docs:

[quoote (regarding CurrentTime)
Returns the current time in the format: HH:MM:SS (i.e. 14:31:57). [/quote]
[quoote (regarding CurrentDate)
Returns the current date in the format: DD MON YYYY (i.e. 10 DEC 2000).
[/quote]

So this seems to answer my question anyway :) but thanks for the responses all the same!


_Skully(Posted 2010) [#5]
oops... nm