Robotics TXT - Date Fields Mismatch
Moderator: fischertechnik Mitarbeiter
Forumsregeln
Bitte beachte die Forumsregeln!
In dieser Unterkategorie können nur fischertechnik-Mitarbeiter und Moderatoren antworten!
Bitte beachte die Forumsregeln!
In dieser Unterkategorie können nur fischertechnik-Mitarbeiter und Moderatoren antworten!
Robotics TXT - Date Fields Mismatch
Year returns day, Month returns year and Day returns month on RoboPro 4.2.3.
Re: Robotics TXT - Date Fields Mismatch
There is an additional glitch for February 29th, 2016.
EDIT Day displays seconds. February 29th is unknown. 29 is changed for 1!
EDIT Day displays seconds. February 29th is unknown. 29 is changed for 1!
Zuletzt geändert von Rei Vilo am 29 Feb 2016, 16:34, insgesamt 1-mal geändert.
-
- Beiträge: 171
- Registriert: 12 Jan 2016, 09:13
Re: Robotics TXT - Date Fields Mismatch
Dear Rei Vilo,
this is a strange bug. Thanks for reporting it. Hopefully, this will be fixed in a future ROBOPro update.
Best regards,
Markus
this is a strange bug. Thanks for reporting it. Hopefully, this will be fixed in a future ROBOPro update.
Best regards,
Markus
Re: Robotics TXT - Date Fields Mismatch
Dear Rei Vilo,
maybe if fixes your "seconds instead of days" problem if you use different variable names for hours, minutes and seconds.
I guess seconds part of your program overwrites day variable content.
Anyway you will get months instead of days again.
Regards,
Robert
maybe if fixes your "seconds instead of days" problem if you use different variable names for hours, minutes and seconds.
I guess seconds part of your program overwrites day variable content.
Anyway you will get months instead of days again.
Regards,
Robert
Re: Robotics TXT - Date Fields Mismatch
Dear Robert:
Thank you for the suggestion.
Unfortunately, variables with different names give the same result.
Thank you for the suggestion.
Unfortunately, variables with different names give the same result.
Re: Robotics TXT - Date Fields Mismatch
Dear Rei Vilo,
yes, it does not fix the day/month/year problem as well as the added leap year problem, but the reported error in your 2nd post (seconds instead of days).
Kind reagrds,
Robert
yes, it does not fix the day/month/year problem as well as the added leap year problem, but the reported error in your 2nd post (seconds instead of days).
Kind reagrds,
Robert
Re: Robotics TXT - Date Fields Mismatch
I tried DayOfWeek, and it provides the day of the month.
So I guess Day provides the day of the week!
So I guess Day provides the day of the week!
Re: Robotics TXT - Date Fields Mismatch
I have the same problem so i cant run my simple clock. https://www.dropbox.com/s/thy176zgpgx1uwq/uhr.rpp?dl=0. In the middle it says ERROR. And my TXT says its the 29th of March.
Raphael
Raphael
-
- Beiträge: 171
- Registriert: 12 Jan 2016, 09:13
Re: Robotics TXT - Date Fields Mismatch
Dear Rei Vilo, dear Raphael,
it seems that there are a lot of bugs concerning the date fields. We will fix this, thanks for the investigations.
Best regards,
Markus
it seems that there are a lot of bugs concerning the date fields. We will fix this, thanks for the investigations.
Best regards,
Markus
Re: Robotics TXT - Date Fields Mismatch
Hi Markus,
i think that these bugs are there since version 4.2.3 because in v 4.1.8 and 4.2.1 (i´m not sure about the number. Mr Kaup has sent this beta to me) my clock has been working fine.
Raphael
i think that these bugs are there since version 4.2.3 because in v 4.1.8 and 4.2.1 (i´m not sure about the number. Mr Kaup has sent this beta to me) my clock has been working fine.
Raphael
-
- Beiträge: 171
- Registriert: 12 Jan 2016, 09:13
Re: Robotics TXT - Date Fields Mismatch
Dear Raphael,
thanks for this info!
best regards,
Markus
thanks for this info!
best regards,
Markus
Re: Robotics TXT - Date Fields Mismatch
What I don't know is whether the problem comes from the translation into English only or also exists on the German version.
-
- Beiträge: 171
- Registriert: 12 Jan 2016, 09:13
Re: Robotics TXT - Date Fields Mismatch
Dear Rei Vilo,
unfortunately, this problem appears in all languages.
Best regards
Markus
unfortunately, this problem appears in all languages.
Best regards
Markus