firstDayOfWeek=1 month view has a bug

brOOper / gwt-cal

Automatically exported from code.google.com/p/gwt-cal

0 stars 0 forks source link

firstDayOfWeek=1 month view has a bug #86

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

When I set as locale of my property file firstDayOfWeek=1 monthview evaluate 
the appointments position wrong. but when I return firstDayOfWeek=0 there is no 
problem at all. IS there any solution for this bug?

Original issue reported on code.google.com by harunate...@gmail.com on 20 Sep 2010 at 3:22

Merged into: #136

GoogleCodeExporter commented 8 years ago

Please attach a sample snippet of java code that demonstrates this issue

Original comment by Brad.Ryd...@gmail.com on 20 Sep 2010 at 5:06

Changed title: firstDayOfWeek=1 month view has a bug

GoogleCodeExporter commented 8 years ago

I attached the java code which helps you. 

When you compiled this codes, please press "Previous Month" button and examine 
carefully the last row appoinments.Their start dates are wrong.

Then please change the line 174 in GoogleCalendarPanel.java to below

CalendarFormat.INSTANCE.setFirstDayOfWeek( 0 );

After that compile and see when pressing "Previous Month" button there is 
anything wrong.

Please help me

Regards

Original comment by harunate...@gmail.com on 21 Sep 2010 at 6:28

Attachments:

GoogleCodeExporter commented 8 years ago

[deleted comment]

GoogleCodeExporter commented 8 years ago

I was checking old cases and I found your case. Do you still have those 
problems?

Original comment by ctasada on 2 Dec 2011 at 9:21

GoogleCodeExporter commented 8 years ago

[deleted comment]

GoogleCodeExporter commented 8 years ago

I may be missing something obvious, but where's the problem?

For what I can see, the AppointmentBuild.java file is exactly the same that's 
available in the SVN repository. The GoogleCalendarPanel.java has some changes, 
but nothing related with settings.

Looking into the generated Appointments I don't see anything wrong. Can you 
please double check with the latest version and confirm that the problem is 
still there? Also, can you point to some specific problem? Maybe removing the 
whole randomness from the AppointmentBuilder and using some static data would 
help.

Regards.

Original comment by ctasada on 19 Dec 2011 at 9:26

GoogleCodeExporter commented 8 years ago

Hi harun, 

Can you check if the fixes to issue 136 are helping?

Original comment by ctasada on 21 Dec 2011 at 9:23

GoogleCodeExporter commented 8 years ago

Hi harun,

No news from you. Is the issue now fixed? if not, can you provided updated info?

Thanks.

Original comment by ctasada on 17 Apr 2012 at 9:36

GoogleCodeExporter commented 8 years ago

Hi Ctasada,

I'm sorry, I couldn't look this bug. I'm very busy nowadays and this bug is too 
last.

I will look it later. If I have a problem I will call you. Ok.

Thanks for your interest.

Best Regards,

Original comment by harunate...@gmail.com on 18 Apr 2012 at 6:18

GoogleCodeExporter commented 8 years ago

Sure!

Original comment by ctasada on 18 Apr 2012 at 7:56

GoogleCodeExporter commented 8 years ago

Marked as duplicate

Original comment by ctasada on 14 Aug 2012 at 7:45

Changed state: Duplicate