I implemented MasterDetailPage into my app, but on Windows 10 the behavior seems a bit weird.
When the app starts, the menu is showing as expected. But when I click an item, it disappears with no way to go back or show the menu again.
It's simple to reproduce.. Download the sample: https://github.com/xamarin/xamarin-forms-samples/tree/master/Navigation/MasterDetailPage
Run the UWP app on Windows 10 and click any menu item. Now you're stuck on that page, with no way to navigate further.
Yes, it's weird.
To somewhat fix this issue, you can use the MasterDetailsPage MasterBehavior property, and change the behavior to one that doesn't seem odd.
You could also use some code to change it only when running on Windows, since the menu works correctly on Android and iOS.
Related
I got stuck in VS Code, whenever i code and change app in MacOS, once i come back to code in VS Code every button i click doesn type any letter, any help?
I've tried to click on any button but every button does weird things like deleting parts or move the cursor, only way is to reboot VS Code app
I create a simple single-view application project, then run it. The simulator shows a quarter desktop. so strange, I want to see a full-screen result.
Try hitting command 1. Or if that doesn't work then see if in the main file (very top of navigation bar) if the box is checked where it says something like require fullscreen or show in fullscreen
I can't find the Debug View Hierarchy button in Xcode.
I've read this:
Xcode 6.1 can't find 'debug view hierarchy' button
and launched my app on the iOS8 simulator but still no luck. Something to do with the Architectures perhaps?
Here's what I'm using:
Check to see if accidentally you have disables User Interface debugging. You can find this option in Edit scheme, check out the screenshot:
Then this button will be back:
Hope it helps someone.
In your scheme settings, accessible via Product>Scheme>Edit Scheme, there is an option called debug executable,
Enable it to make the debug buttons available
On the left side of the debugger, in the toolbar below:
It is the second icon from the right in the image. It might be black or greyed out depending on whether Xcode is in focus or not.
It works fine on device and simulator. Either click it to break or break using a breakpoint/debugger and use it.
Thanks #Tibin Thomas and #Khaled Barazi. The Debug View Hierarchy button only appears if you have
checked the Debug executable box and
run your app on the simulator.
By the way, in Xcode 13.1, the button have already become as following icon
An application has an NSPopover with some user inputs in the status bar and some windows. The windows work fine but when I open the popover in the status bar it opens inactive. I can see everything but it's all greyed out, like it's a background window. I've been trying everything I can find on activate, activateignoringotherapps, makekeyandorderfront, etc but none of these is having an effect. How can I shift the focus to the statusbar popover?
I also made a button in the window that showed the same popup to make sure it is working, when called from the window button it works perfectly from there. Then I click on the status bar, and it opens from there instead, but inactive.
Thanks for the help.
I've run into the same problem and haven't found a solution. Unfortunately, I believe this is a bug: http://www.openradar.me/radar?id=1226415
There's a framework called SFBPopovers which provides similar functionality and works fine with the menu bar.
It might help with your issue.
I've been playing around with a statusbar menu app and what I'd like it to do is to update the content of the menu when it is clicked. I've been able to get everything working on the awakefromnib function and it works as expected. Now i just want to update the menu everytime I click on the status bar. This surely can be done, since it's done in the dropbox statusbar menu and many of the native app statusbar menus. I'm not able to associate a action directly with the click of the menu and I don't want to leave a loop running in the background cause I don't really see a need for it. Any ideas? An alternative would be to have an action associated to a menu item which does not cause the menu to get hidden again. Any help would be welcome.
Just set a delegate for your menu, and implement the -(void)menuWillOpen:(NSMenu *)menu method.