My Menus in the frontend have gone missing. In the backend, the menu manager shows the number of published menu items in each menu type but when i click to edit the MenuItem(s), i see no items.
Why are the MenuItem(s) missing or not visible? How do i make them visible again?
The site was developed with Version 1.5.10 but the hosting provider(who is not responding) might have upgraded to 1.6 or higher
Look in the menus manager for spaces or special characters in the unique menu names. You should stick to letters and numbers, no spaces, no special characters in menu names. This was not an issue in 1.5.10, the code changed in in a later update that caused this issue.
Related
I used Phrase lists in LUIS in the past. However, the entry is not visible in the left menu anymore even though the documentation says it should be there:
Open your app by clicking its name on My Apps page, and then click Build, then click Phrase lists in your app's left panel
Are Phrase lists removed from LUIS?
Please see this screenshot:
A recent fix was deployed. Please refresh the page
The latest version of macOS Sierra adds a 'Show/Hide tab bar' menu item to the 'View' menu.
It does this dynamically.
My application already includes its own tab bar using the MMTabBarView library. I would prefer to continue using this library as it gives me backwards compatibility with tabs, plus the ability to do some customization to tabs.
I'm not seeing anything in apples NSDocument or NSDocumentController documentation on removing this menu item.
Does anyone have any suggestions as to how I can remove it?
NOTE: I do not want to simply disable it, I am looking to remove it completely. (Or I guess not have it added in the first place).
In Interface Builder, open the attributes of your NSWindow and you'll see an option called "Tabbing Mode". Set it to Disallowed.
Lately in Xcode 5.1.1, my Related Items menu (Control-1) doesn't list Callers.
Is there a workaround to make it appear again?
The listing in the menu is content related.
So in Storyboard no Callers are given.
In a code module (.m) the list does nicely appear in my Xcode 5.1.1
In my case the issue was the Version editor was open. (e.g. Comparison, Blame, Log.)
When the version editor is open, Callers doesn't show up in the context menu.
My application is context-sensisitve and I dynamically build menus for the main window / context/popup, and other places. I typically know if a given menu command will be valid given the current state of the application. Is it better practice to DISABLE/GREY the menu options which currently do not apply OR since I'm generating the menu anyway, OMIT them entirely?
The application is a Java/Swing is anyone is curious. The question seems GUI toolkit agnostic but may be platform dependent.
The old apple guidelines say to Disable for fixed menus (in the menu bar), and omit for context menus.
I guess the motivation is that a context menu is supposed to only show options that are available to the particular context, and the main menus are supposed to show all commands, so the user knows where "Save" would be even if it's not selectable at the moment.
For right-click menus, I'd say that if the item is applicable to what was right-clicked but is for some other outside reason unavailable, disable it. If it is not applicable to the right-clicked thing then hide it as there's no chance of it ever showing up. Case in point:
When I right-click on the background area of this page in Firefox the first four items are Back, Forward, Reload, and Stop. Forward and Stop are disabled because they aren't valid actions right now (I have no forward history and the page is not loading anymore). These four guys are very consistently offered, they are expected, global, often-used commands. They are the four main "navigation" controls and by default they have toolbar counterparts (in the form of big dedicated buttons).
However, if I right-click on an image, I get completely different options in the context-menu all related to viewing, saving, and copying the image under where I clicked. These options don't appear at all (not even disabled) under normal use because they are very specific to what I right-clicked on. When right-clicking on the background area, Stop and Forward, while currently not valid actions, are still applicable to what I clicked on (the page) but they are unavailable for other reasons...
Like the rule for menus on the top menu bar, the goal is not to surprise users with commands suddenly appearing for, from the user's point of view, inexplicable reasons.
TextMate has one irritating 'feature' that shows up when editing lot of files (within a given project). in case there is no place at tab bar for new tabs, a ">>" is shown. it simply shows a popup with rest of files. that's ok, but why when one selects a file its tab is not visible? isn't it kind of iconsistency? what is more irritating here, tabs are not shown in this case even when navigating through "Next File Tab" or "Prev File Tab".
is there any way of enabling "scrollable" tabs bar or it's just "feature, not a bug" ?
This is just a byproduct of TextMate's tab-handling code (which is believe is custom-written for TextMate). I wouldn't call it a "feature" nor a "feature, not a bug", because I think it is a bug, just one that hasn't been fixed yet (development TextMate 1.x has been rather stagnant for the past couple of years). But I don't think there are any plugins that fix the bug and enabled a scrolling tab pane.