Announcement

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

    Menu placement on tablet devices

    Hello, I just realized that the Menu.placement is "fillScreen" only on handset devices. In this regard, it has a different behavior from Select/ComboBoxItem where the placement is fillPanel also for tablets.

    May I ask if in your experience this is actually the best behaviour for users, or if you found yourself changing this setting?

    #2
    In implementing apps for customers, we have never actually changed this setting. It's a bit hard to imagine a case where using "fillPanel" would be wrong for a tablet, as the notion of "panel" in this case is a panel of a SplitPane / TriplePane.

    So perhaps something like: there's a Tree on the left, and it's filterable via a comboBox in the same panel. But that comboBox shows multiple fields, even though the Tree being filtered shows only one, so the comboBox shows excessive clipping when confined to the same space as the Tree it is filtering.

    That case is pretty rare, and hasn't come up in apps we've built for customers. But it could come up, and if so, changing to "fillScreen" in that case makes sense.

    But we would recommend leaving the default of "fillPanel" on tablets alone, because generally on a tablet, you have enough screen real estate that it's better to continue to show part of the screen when a comboBox opens, rather than cover everything. It helps the user maintain context about what screen they are on and what they are up to, especially because users are often distracted mid-task.

    Comment


      #3
      Hello, thank you for the clarifying response regarding Select/ComboboxItem.

      However, I still have a doubt regarding the Menu, which on tablets behaves by default like on desktop, whereas I would have expected a default placement of fillPanel as with SelectItem.

      Comment


        #4
        Oh, you were asking the reverse? Are you saying that fillPanel seems a better default for Menu on the tablet form factor, whereas in fact it's fillScreen by default?

        Comment


          #5
          actually I'm saying that the default seems to be the same as on desktop, on tablets:

          https://smartclient.com/smartclient-...Menu.placement

          this is what I see using the simulator:

          Click image for larger version

Name:	2024-05-10 21.54.04.jpg
Views:	175
Size:	72.1 KB
ID:	272332
          Attached Files

          Comment


            #6
            OK, now we see. So the answer is still "no" - we've never, when building an app for a customer, changed the default Menu.placement to either "fillPanel" or "fillScreen" for the tablet form factor.

            As we mentioned above, in general, it's better to keep the rest of the UI visible, if there's plenty of screen real estate for the Menu or ComboBox.

            The main reason we could see for using fillPanel/fillScreen placement for a Menu on the tablet would be if the menu had so many items that it was required to scroll. In that case, the fillPanel UI might offer quicker or more usable scrolling. So perhaps an improved default would be to use "fillPanel" if there are enough items to require scrolling.

            Are you asking because you frequently find yourself setting custom placement for Menus on tablet?

            Comment


              #7
              Hi, actually, I don't have much experience using SmartClient apps on tablets. However, I am currently evaluating the usability of an application that will definitely require some adjustments.

              For some reason, I remembered that the menu on tablets did not use the same mode as on desktop. So I had some doubts about the usability with touch devices, but now that I have tested it on a physical device, it seems to work well. I hope users won't give me different feedback. Your suggestion to use fillPanel for large number of items makes sense tho.

              Comment


                #8
                Originally posted by Isomorphic View Post
                The main reason we could see for using fillPanel/fillScreen placement for a Menu on the tablet would be if the menu had so many items that it was required to scroll. In that case, the fillPanel UI might offer quicker or more usable scrolling. So perhaps an improved default would be to use "fillPanel" if there are enough items to require scrolling.
                Hello, while trying the sample https://www-demos.smartclient.com/sm...&skin=Twilight with an iPad, I found that it's really really difficult to scroll the menu when it doesn't fit on screen (Go to category -> General Office Products).

                Also it seems *impossible* to scroll the menu in the iOS simulator. Do you have the opportunity to try?

                Comment


                  #9
                  We are in the process of making a few different improvements in this area that affect iPad. We'll update this thread when they're complete.

                  Comment


                    #10
                    We've made several fixes to address issues related to the menus in the "Tree Binding" Showcase sample on tablets and elsewhere. These have been applied to SC 12.1+ and will be in the nightly builds dated 2024-07-25 and beyond.

                    Comment


                      #11
                      Hello, I see it's much much better, thank you very much.

                      Maybe when a menu has items which are both clickable and have got submenus, I'll still prefer a different placement, for the less skilled users, but for now I haven't got this use case.

                      Comment

                      Working...
                      X