Announcement

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

    Icon for Columns from ListGrid Context menu when Field Picker is used

    Hi Isomorphic,
    We use ListGrid with setUseAdvancedFieldPicker(true)like in this showcase http://www.smartclient.com/smartgwt/...e_field_picker.
    We noticed that usual icon for MenuItem "Columns" is not presented if we click on grid context menu. But it exist for other cases where advancedFieldPicker is not set to true.
    For example in this showcase http://www.smartclient.com/smartgwt/...ce_columnorder
    Is it an expected behaviour?
    From out point of view it looks inconsistent and we need to provide some hack to make this image visible for grid with AdvancedFieldPicker.

    Best regards, Ksenia

    #2
    We've altered to show the same icon in all cases - you didn't mention your version, but you can retest with a build of 5.1 or later, dated January 15.

    Comment


      #3
      Hello, Isomorphic.

      Thanks for your support. Unfortunately we use 5.0 version. Is it possible to port the fix to it?
      Thanks in advance and sorry for disturbance,

      Best regards,
      Iaroslav

      Comment


        #4
        Yes, we can port this one back to 5.0 - you can test it in builds dated January 17 and later

        Comment


          #5
          Hi Isomorphic,

          Thank you for the fix.
          Now we see the icon for the Columns but we still have view inconstency in the separators around this Menu Item.
          For example usual Columns menu item (without field picker) is surrounded by separators, but menu item Columns with fieldpicker is not.
          I attached printscreens.
          Is it possible to fix it also ( for 5.0) ?

          Click image for larger version

Name:	withSeparators.png
Views:	209
Size:	62.2 KB
ID:	242308


          Click image for larger version

Name:	withoutSeparators.png
Views:	222
Size:	114.2 KB
ID:	242309


          Best regards, Kseniia.

          Comment


            #6
            We've made this small cosmetic change badk to 5.0 - however, note that you should upgrade to 5.1 when possible, since we may not always be able to port more complex changes to all historical versions - in that case, we may only apply such patches to the latest minor version of each branch - so 5.1, but not 5.0.

            Comment


              #7
              Thank you for the quick answer.
              Did I understand correctly that this fix will be available since build dated 18 January?

              Comment


                #8
                This change, yes - it's already hit the build queue for tomorrow's builds.

                Comment

                Working...
                X