Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    #16
    Any fix in the works?

    Comment


      #17
      We're not seeing this issue against latest 4.1d - make sure to clear your browser cache and run a GWT compile

      Comment


        #18
        I am still seeing the problem at the SmartGWT Showcase. I have cleared my cache and reloaded the page using CTRL+F5.

        Comment


          #19
          This definitely looks like a caching issue.

          If you're talking about the Showcase online at smartclient.com, nothing has changed there - we don't run the latest build on the website. You need to test with the showcase in the latest nightly build.

          Either way, you need to make sure you navigate away from your page before clearing your browser cache, and make sure, as we said, to run a GWT compile.

          Comment


            #20
            Yes, I have always been talking about smartclient.com from the beginning. That's why I referenced the site in the first place.

            Comment


              #21
              Except for this comment: "same problem in FF 26.0 in deployed app built with current 4.1d." - that's not talking about the website and is why we've spent so much time looking into it.

              For future reference, the Showcase running on smartclient.com does *not* run the latest build, and it never has. This is why we always request that you test against the latest from smartclient.com/builds.

              Comment


                #22
                Ok, that's fine except that wasn't my comment. I know now that smartclient.com doesn't run the latest (though it probably should since your latest version is always considered the most stable).

                Comment


                  #23
                  Originally posted by Isomorphic View Post
                  Except for this comment: "same problem in FF 26.0 in deployed app built with current 4.1d." - that's not talking about the website and is why we've spent so much time looking into it.
                  That was my comment. I meant my app, not the showcase in that comment. Sorry for not being clear (but it shouldn't matter as it was the current daily at that time I used to build the app).
                  The video I provided later was from the datepicker in a generated MiniDateRangeItem in a ListGrid of my app.

                  But I can confirm that the effect is gone now with my app and current SNAPSHOT_v9.1d_2014-01-22/EVAL Deployment, so you must have fixed something between Jan, 16th and Jan, 22nd.

                  Best regards,
                  Blama

                  Comment


                    #24
                    Yes we did, on 17th, see post #6 in this thread

                    Comment


                      #25
                      Hi Isomorphic,

                      sorry to bother you again. The chooser for a "date" files is fine now. The chooser for a "datetime" field is broken with current 4.1d nightly, at least for the German localization, where the strings on the buttons are longer than in English.
                      It is not the same bug as before, but in the same area, so I didn't create a new bug report.

                      Please see the attached screenshot.
                      Steps to reproduce:
                      1. BuiltInDS Sample
                      2. Add <extend-property name="locale" values="de" /> to BuiltInDS.gwt.xml
                      3. Change date to datetime in supplyItem.ds.xml, field nextShipment
                      4. Start DevMode
                      5. Go to http://127.0.0.1:8888/BuiltInDS.html?gwt.codesvr=127.0.0.1:9997&locale=de


                      Best regards,
                      Blama
                      Attached Files

                      Comment


                        #26
                        What bug are you pointing out?

                        Comment


                          #27
                          Hi Isomorphic,

                          please see the attached screenshot in my last post and compare to an English version screen, e.g. this sample.

                          In English sample: Top row ("Jan 2014") has rounded corners and a fading background.

                          In German screenshot: Top row ("Jan 2014") doesn't have a fading background the whole width, only in the area where there are dates below. This is because the whole window has become wider because of the longer strings.

                          It's not a framework bug like the original bug this post was about, but a not-perfect out-of-the-box-component.

                          Best regards,
                          Blama

                          Comment


                            #28
                            Ah, so by "broken", you just meant that the layout with the header-buttons and the grid in it is the same size as the English version and is centered, rather than filling the width of the DateChooser?

                            That's by design, we support showing other columns too (fiscal year, week).

                            If you don't like that effect, you can alter it via the autoChildren on DateChooser (navigationLayout and dateGrid)

                            Comment


                              #29
                              Ah, OK. Thanks.
                              I think I will disable the time-part (and apply button) by setShowTimeItem(false).

                              Just out of interest (won't use it now) regarding autoChildren: How do I know the possible values of the autoChildName-parameter in DateChooser.changeAutoChildDefaults(java.lang.String autoChildName, Canvas defaults) (or for any other item with AutoChilds)?

                              Best regards and thanks for the fast answer,
                              Blama

                              Comment

                              Working...
                              X