3 Replies Latest reply on May 8, 2009 10:14 AM by ilya_shaikovsky

    3.3.1 - Shared calendar creation (Problem)

    krasig

      A few days ago I reported this: https://jira.jboss.org/jira/browse/RF-6950.
      But after some investigations I realized that problems are not in calendar.
      I use this http://www.jroller.com/a4j/entry/richfaces_calendar_component_shared_calendar for my pages and with 3.3.0 all is OK. But with 3.3.1 CR2 in calendar no digits in days square
      see pic: http://screencast.com/t/Lg69TxBxFGG

      Any idea how to resolve this problem ?

        • 1. Re: 3.3.1 - Shared calendar creation (Problem)
          ilya_shaikovsky

          yup.. actually this thread is no more actual. we finally solved the optimization issue. now calendar all the calendar initialization called only on opening. So using the workaround no more necessary and could have such side effect(probably now to use the described workaround we need also to call initialization).. I'll update the jroller post (thanks!) And you just use the calendar as in simple cases and should see the same performance as using suggested workaround.

          • 2. Re: 3.3.1 - Shared calendar creation (Problem)
            krasig

            Thank you Ilya. I will check the new performance.

            • 3. Re: 3.3.1 - Shared calendar creation (Problem)
              ilya_shaikovsky

              Just missed simple thing. Sure if you need to tune it more and use the article. (1 object is better than many even with optimized code) you should take into account that some calendar code changes after the jroller post was submitted.

              currently I added

               if(!this.isRendered){this.isRendered=true;
               this.render()
               }
              

              after
               if (this.isVisible) {
               this.doCollapse();
               if (input==this.customInput)
               return true;
               }
              
              

              block and all works fine again for me.

              Thanks for your point.. I'll update the jroller post with the warning about this :)