I had this error and want to confirm that its not just me.
Can someone else please try this with a DateTime box; if it is a real bug, I'll log it formally.

Returns an error even though both are date Types.
Error returned is : "Type mismatch: Wanted Date , got string instead."

Gambas=3.12.90
OperatingSystem=Linux
Kernel=4.15.0-46-generic
Architecture=x86_64
Distribution=Ubuntu 18.04.2 LTS
Desktop=UBUNTU:GNOME
Theme=Gtk
Language=en_AU.UTF-8

 Where are you getting a DateTime box? The only thing I can find is a ValueBox with the type set to DateTime. Maybe I'm missing a component that has that?

 Hey Sholzy,
Got actual control name wrong…..

DateBox (gb.form)
This control allows to edit a date value. It provides a little button that displays a calendar popup.

Edit: in the 'Chooser' tab.

 You must to share more code to allow us to understand your error. Tested here without problem.

Also the date must be in us style mm/dd/yyyy. in other case it return the message you have

I can just say the pb is around your use of CDate

Quincunxian said

I had this error and want to confirm that its not just me.
Can someone else please try this with a DateTime box; if it is a real bug, I'll log it formally…

No, it seems to work as expected for me on 3.12.90 (…and on 3.12.2).

The error message: "Type mismatch: Wanted Date , got string instead."
…is a funny one, because I often see this when the error is unrelated to this description (its almost like a fall-back error).


Edit: I'm running 3.12.90 on Lubuntu 18.10 with that new LXQt desktop

I did this in a Form_Open():

    
I got this in the console:


The date was also 12/31/2018 on the form.

Looks like a bug to me.

It also raises the question, how does one place a Form control on the form at design time if it isn't in one of the panels to the right?

Ced

3.12.2 (Behind the front lines.)

 I tried this and it works as expected. Is this a language problem?

I am using  en_GB.UTF-8 (British)
Stevedee   en_GB.UTF-8 (British) - I presume
Quincunxian en_AU.UTF-8 (Austrailia)
Cedron en_US.UTF-8 (USA)  - I presume
Sholzy en_US.UTF-8 (USA)  - I presume

Just a thought!

Cedron .Move() does what you four lines did in one

/comp/gb.qt4/control/move - Gambas Documentation

@Cedron .Move() does what you four lines did in one

I did not need either the following worked fine: -

cogier said

I did not need either the following worked fine: -

Sure, but that's another story  

 Again it work fine for me :-/

So the problem can coming from your system too.

cogier said

@Cedron .Move() does what you four lines did in one

I did not need either the following worked fine: -

Code (gambas)

1. Public Sub Form_Open()
2. Dim d As DateBox
3.  
4. d = New DateBox(Me)
5. d.Value = CDate("01/01/2019")
6. Print d.Value
7.  
8. End

Thanks, I should have remembered that.  Honestly, it's not all that often that I move controls around the form.

Code:

Output:

Somebody is definitely having trouble getting a date.

(Side note:  Could you guys put one of those handy "SELECT ALL" options in the "gb" tag output?

Ced

[System]
Gambas=3.12.2
OperatingSystem=Linux
Kernel=3.13.0-24-generic
Architecture=x86_64
Distribution=Linux Mint 17 Qiana
Desktop=MATE
Theme=Gtk
Language=en_US.UTF-8

It works OK for me.

<IMG src="http://www.cogier.com/gambas/date.png"> </IMG>

You can change line 10 to: -
Same result.

Somewhat tracing what happens in the code (shown below)


Produces:


So I am a bit puzzled.  I've always understood internal date representation to be Integer Date + Fraction Of Day Time.

Looks like Str and Val might be problematic.

Ced

From: gambas-master/comp/src/gb.form/.src/Date/DateBox.class

It helps to RTFM.  The Str$ vs CStr is a localization issue.

/lang/cstr - Gambas Documentation

vs

/lang/str - Gambas Documentation

Same with val vs CDate.

So, val and str use localization, CDate and CStr do not.

Hence the observed behavior.

I have not been able to reproduce the OP's original bug.

Ced

Ok that makes sense now.  :roll:
Thanks to all.

I've been keeping a list of things that are either bugs(?) that need to be confirmed or a bit of a wish list.
I'll post in a new thread with a more appropriate title a bit later on.

 This work for me:
DateBox1.Value=CDate(CDate("01/01/2019")+1)

chescobar said

This work for me:
DateBox1.Value=CDate(CDate("01/01/2019")+1)

It might not have 2 years ago when the post was made