Could SER get a way to buffer the choices in the Category pull-down menus on target sites?

…because I’d like to translate them and learn the phrases that constitute the various categories in different languages.
If there was a way to save the choices, just so I can enter them into G! translate and make a cheat sheet I print out or have in a file so I can learn them, that would be very useful.
Hope all you guys and girls are having a fun weekend.  :)

Libreoffice has no menubar in Kubuntu 18.04 if Application button (for global menus) is added on window titlebar

It looks like a bug but I am not sure which program is to blame..

In Plasma 5.12 the option to add global menus in window titlebar has been removed. There is a panel widget that adds global menus to the panel, but also global menus are still available in the window titlebar as a button. I have added that button with global menus as indicated here. That’s under System Settings > Application Style > Windows Decorations > (tab) Buttons:

enter image description here

The idea is to get the global menus into a left-side button on the window upper margin; like for example in Chrome:

enter image description here

When this is done, Libreoffice has no menubar anymore. Adding the Menubar button and using it has no effect.

enter image description here

But once the “Application” button is dragged away from the titlebar at System Settings > Application Style > Windows Decorations > (tab) Buttons, the menubar in Libreoffice comes back.

enter image description here

Clear region with menu’s per url cache

I have a region with menus, a menus displays depending on the url example if on the about page(sitename/about-us), display about menu and links as a sub menu.

It works, but the problem is after navigating through the site a couple of times, the region caches. is the anyway i can clear the regions cache on page reload.

I tried the below in my .theme

/** * Implements hook_preprocess_HOOK() for block.html.twig. */ function themename_preprocess_block(&$ vars) { the menu block id name in the region if($ vars[‘derivative_plugin_id’] == ‘submenu’) { //– This stops the block being cache in drupal 8 $ vars[‘#cache’][‘max-age’] = 0;

} }

also tried

/** * Implements hook_preprocess_HOOK() for block.html.twig. */ function themename_preprocess_block(&$ vars) {

if($ vars[‘derivative_plugin_id’] == ‘theme-block-branding’) { //– This stops the block being cache in drupal 8 $ vars[‘#cache’][‘max-age’] = 0;

} }

not sure what steps I can follow to achieve the above

What is the significance of the three dots “…” on menus and buttons and how to use them right?

Adding three dots after the title of items in a dropdown menu seems to be a common practice (as you can see on the picture of a drop down menu in Google Chrome). They generaly mean that there is “something” after clicking on it.

Google chrome dropdown menu (french version)

These dots are also sometimes presents in the text of action links and buttons.

I am wondering about their utility and relevancy…

In your opinion :

  • What kind of information should be conveyed by these dots ?
  • How and when to use them ?
  • Is it realy relevant to the user, and easily understood by them ?

How to always show keyboard accelator keys for popup menus?

When opening a popup menu in Windows via the right mouse button, ever since Windows XP, the accelerator keys (i.e. the key to choose one of the popup menu items) are not visible anymore by default. Supposedly there is a way to set this as default behaviour, but where?

If I use Shift+F10 or the menu key (right of the space bar), the accerator keys are shown.

I only found this Delphi-specific question, there answer to which points to the existance of such setting but does not state where: Stack Exchange

How do I programmatically render a menu’s label?

I’m trying to render out a menu with its label in Drupal 8. I am able to get the menu and its links inside of a preprocess function using a helper function, but I can’t locate the menu’s title.

Here is how I’m getting the menu. I’m able to add the return value as a twig variable $ variable[‘menu’][‘menu-name’] and render out an <ul> anywhere I need to.

function get_menu($  menu_name) {   $  menu_tree = \Drupal::menuTree();   $  parameters = $  menu_tree->getCurrentRouteMenuTreeParameters($  menu_name);   $  tree = $  menu_tree->load($  menu_name, $  parameters);   $  manipulators = array(     // Only show links that are accessible for the current user.     array('callable' => 'menu.default_tree_manipulators:checkAccess'),     // Use the default sorting of menu links.     array('callable' => 'menu.default_tree_manipulators:generateIndexAndSort'),   );   $  tree = $  menu_tree->transform($  tree, $  manipulators);   $  menu = $  menu_tree->build($  tree);    return array('#markup' => drupal_render($  menu)); } 

Custom menu is rendered in all menus

I am currently working on my own theme. In this theme I want two menus topmenu and bottommenu.

In the functions.php file I have the following code:

// This adds the support to add a thumbnail and custom menus function thumbnail_menu_support() {     add_theme_support( 'post-thumbnails' );     register_nav_menus(         array(             'topmenu' => __( 'Top menu' ),             'bottommenu' => __( 'Bottom menu' )         )     ); } add_action( 'init', 'thumbnail_menu_support' ); 

In my header.php and in the footer.php I have the following code:

<?php wp_nav_menu( array(     'menu'              => 'Top menu',     'menu_id'           => 'topmenu',     'container'         => false,     'fallback_cb'       => false,     'theme-location'    => 'topmenu' ) ); ?> 

and

wp_nav_menu( array(     'menu'              => 'Bottom menu',     'menu_id'           => 'bottommenu',     'container'         => false,     'fallback_cb'       => false,     'theme-location'    => 'bottommenu' ) ); 

Now, when I make a menu in the backend of WordPress, and specify that it should only be in the top menu, it will be rendered in both menus.

See this: enter image description here

Is there a rule of thumb for whether I should hide the navigation menus on scroll?

I’m working on an Android app, and I’ve implemented layout behavior to hide the top app bar and the bottom navigation menu on scrolling a list page.

At the moment, I just did it because I could and it seemed like a nice-to-have for the software architecture from a developer’s perspective, which I realize is often at odds with UI and UX.

I’ve gone through hundreds of mobile app UI and interaction designs on Dribbble and I haven’t been able to figure out a pattern to when this scrolling behavior is used yet.

Could someone please provide their decision making process when it comes to whether the bottom navigation menu should be hidden on scroll or persistent?

My app will have 5 different top-level pages that can be reached from the bottom navigation menu. It’s likely that any list in these pages will have about 2 full mobile screen lengths of content at most, which is what made me question whether I was really doing the right thing.

Some of the questions I ran into are below.

  • Is this generally a UI pattern best served for infinite scrolling apps or does it have its uses for smaller static lists as well?
  • Should I hide both the top bar and bottom navigation menu? Or keep the bottom navigation menu and only hide the top bar?
  • I’ve noticed a lot of the really visually appealing designs have a persistent top bar. Is this a sentiment shared by others or is it just me? It seems like it’s easier to make a page look good when the toolbar and navigation menus are static, while hiding them only leaves a boring looking list to look at.
  • Is there a minimum amount of data you require before using this pattern? e.g. I have a page with about 15 list items, that might not require this pattern. However, the search functionality on this page looks for data one level deeper which can result in a 100 items. Would you then implement this pattern for both the list and search results? Or just the search results? Or not at all for both cases?
  • With mobile screens getting larger, will this pattern become less beneficial or are there still other advantages regardless of screen size?

I don’t really need answers to every one of these questions, but I’d really love to know the thought process that goes into navigation menus and scrolling decisions.