[pratik.thaker]

Hi Isomorphic,

Can you please let us know whether this issue has been resolved in SmartGWT 4.0 ?

[jayeshecs]

List of fixes added in all 3.1 patches

Hi Isomorphic,

Is there a way to get list of fixes added in all 3.1 patches. It seems we are using very first released version of 3.1.

Thanks,
Jayesh

[jayeshecs]

Seems to be working fine on latest build 3.1p/LGPL/2014-01-23

Hi Isomorphic,

Things seems to be working fine with latest build 3.1p/LGPL/2014-01-23.

We would initiate a regression of our app with latest build to find out any potential issues.

Thanks for the help.

Cheers,
Jayesh

[Isomorphic]

What *exact* build number are you on? We don't see any issues against latest 3.1, so if it's not the latest nightly, please try that before reporting issues.

If it *is* the latest nightly, please retest with today's build, which will be at smartclient.com/builds shortly, because a change was made yesterday that may address this for you.

[pratik.thaker]

SmartGWT 3.1 (LGPL), GWT 2.5, FireFox 24

Hi,

Please find attached screenshot which shows that the issue is being reproduced with the give test case.

[Isomorphic]

This test case works as expected for us against latest 3.1 - that is, typing in a valid date and then clicking the Picker icon shows the popup DateChooser with appropriate Month and Year headings.

Please confirm if those are the actions you're taking that result in this issue you're seeing, and that you are using the latest build of 3.1 from smartclient.com/builds.

[jayeshecs]

This issue exists for SmartGWT 3.1 + GWT 2.5

Please find attached test application using which the issue of showing incorrect month and year on header can be replicated.

Attached are four source files good enough for replicating this issue.

DateTextItem.java (6.0 KB)
SmartGwtTestbedEntryPoint.java (854 Bytes)
SmartGwtTestbed.gwt.xml (1.0 KB)
SmartGwtTestbedHtml.html (541 Bytes)

Please note that this would require gwtx-1.5.2.jar for SimpleDateFormat GWT implementation.

Thanks,
Jayesh

[Isomorphic]

It's fine to use SmartClient within a regular web page. It's not OK to use a SmartClient widget, such as a FormItem, and then reach in and access or modify the DOM generated by that SmartClient widget.

However, on a second look, you used the name "FormItem" but you were actually just working with a native <input> element that you directly created. This, in itself, is fine.

However your means of constructing and parsing dates is still wrong, and is the reason your test doesn't work - you need to look at the logicalDate, logicalTime vs datetime discussion in the Date Overview we referred you to, and use the documented helper methods for correct construction of dates and times.

[asingla]

I read the link and I was aware of most of facts but I am still not sure what's wrong with my test case.

In our web application, we have pages based on smartclient as well as regular HTML pages. Now in one of the regular page we have to use Calendar. So to be consistent with other pages for date picker (calendar), I decided to choose DateChooser.

As per the docs, I believe DateChooser is an independent component and I have used this as per the docs (getData and setData). I will appreciate if you can tell me what's wrong in the code or any other way I can use this calendar widget in my regular html pages.

[Isomorphic]

In general, use search to find any document we refer you to. Here's a link. Read about logical dates vs logical times vs datetime values and APIs to correctly obtain and convert between these (which is actually incredibly tricky).

Separately, your test case directly reaches into the generated DOM, which is considered internal, and is invalid to directly access.

[asingla]

Ok. As per the latest build, DateRangeDialog is working correctly but the issue is reproducible against SmartClient_v83p_2012-11-27 build. So there was an issue.

That said, code written by me is still not working.

Where I can find "Date Format & Storage overview" and I will appreciate if you can tell me the issues in the code.

[asingla]

So you are saying that it was a bug (as its reproducible on your feature explorer) and has been fixed in the latest nightly build.

[Isomorphic]

Broken code that happens to work in 8.2 isn't guaranteed to work in 8.3, that's why we ask that you stick to documented APIs.

Again, please look over our previous comments; if you provide a valid test case showing a bug, let us know.

[asingla]

I tested with latest nightly build (SmartClient_v83p_2012-12-12_Pro.zip) downloaded today and was able to reproduce this issue.

I am not sure what issues you are referring with the code, but this same code was working with 8.2

Ignore the last line in the code.
this.datePicker.reflowNow();

[Isomorphic]

If you test with the 8.3 docviewer files you are not testing with the latest patch build.

You have a bunch of usage issues in your code, including direct access to DOM elements managed by SmartClient, and what looks like bad date handling code - read the Date Format & Storage overview for details.

If you can produce a test case without these issues that's actually been tested against the latest patch build, let us know.