Hover Previews enable users to automatically preview files while browsing the context menu created by FolderGlance, without using the keyboard. Educational Institution and Student Discounts.Without rich text, the default foreground colour of menus is automatically in contrast to the background, whether dark or not, but with rich text enabled it’s always black. As I said, the one thing I would rather not change in any menu or menu item is its colour, especially if it has to be item-by-item rather than per-menu. In both cases, colour definitions are ignored *, both for the whole menu and an individual item, and the foreground colour remains black whether in dark mode or not. let theMode=tagdata(applescript(),"dark mode:",",",1) Here is an example I put together to set all the menu items to red if my system is not in dark mode and white if it is in dark mode. If you declare the color on the main menu title then all the following menu items will default to that color unless individually changed in the remaining menu items. How easy would it be to tweak things to use the OS default foreground colour (white for highlighted items and black or white, as appropriate, for the rest) in RTML menus too? Speaking for myself, there are several markup options which I might consider applying to menu items apart from italic - bold, justification, etc.- but colour would not be one of them. Whether enabling RTML in a menu or not, it would be foolish to choose any foreground colour except one that would stand out against any likely background (e.g. However, non-RTML menus also allow the foreground colour to be changed (of the whole menu item) yet observe the OS′s default black or white if it isn’t. I can see the logic for enforcing a fixed default foreground colour when RTML provides the tag to enable colour to be changed selectively, just as HTML does. However, that would be cumbersome, would make the menu variable significantly longer and the menu perhaps slower to display, and, most important, it would make the menus completely illegible if dark mode were then disabled (0xffffff on 0xf6f6f6 is not a good look - less than 4% difference between the colours!) Since I usually use dark mode, one way round this would be to add ‘ color:ffffff’ to every item in every menu and submenu. However, when RTML is enabled using #RichText ’, the default foreground colour is always black, regardless of whether or not dark mode is selected, or whether the item is highlighted or not - and black text doesn’t show up well against a background colour of 0x373737. In this particular dataset it’s important to be able to use italics for individual words within each menu item, therefore the ‘ General > Use dark menu bar and Dock) Therefore it’s important to assemble all submenus in the right order in the variable to be passed to ‘filemenubar’ (or whichever command). The only temporary stumbling block was realising (which should have been obvious) that not only do all submenus have to be defined before the main menu, but all sub-submenus must be defined before the submenu to which they are attached, and so on up the tree. And, thanks to LMSL, it was much easier than I expected: very straightforward to build each submenu as a text array, using the appropriate primary key as the name of each of the many nested submenus. Therefore creating a menu tree for the data set I’m working on was a higher priority for me than a search form. In a group of databases containing structured data, from which it is possible to analyse the tables to present it in a hierarchical manner, I find it useful to present that hierarchy as a menu tree - just as I almost always find a hierarchical menu (such as Classic Menu or Folder Glance) the quickest way to locate a file on my various hard drives.
0 Comments
Leave a Reply. |