I am able to use the shortcut to go back and forth if I only have one view.
But sometimes when I open a split view to work on some specific file. If in this split view I ever go to the file opened in the main view. Then my cursor is moving to the main view, which annoys me.
Is there a way that I can just move back and forth in the particular view. Or in another way, is there a way for me to work on a file in a separate window completely independent. Like having two IDE openings same project.
Related
Consider the following scenario. I have an app with two windows:
the main window which contains all of the app's functionality;
and an auxiliary window that can be invoked using a global shortcut or by clicking app's status bar icon. It looks like this:
It's a simple window for quickly adding data to the application without bringing up the main window — possibly changing spaces and disrupting user's workflow.
The window floats above everything else (it's on NSModalPanelWindowLevel) and can join all spaces (NSWindowCollectionBehaviorCanJoinAllSpaces)
Here's the problem: when the quick-add window is ordered out (the X button or Esc is pressed), the main window is made key and ordered front (provided that it's somewhere on the window list in the current space).
This isn't the behavior I want. Normally, when an app's window is closed, yes, you want the app's window below to be activated, but not here — this is a "helper" window that should work more-or-less independently from the app itself. When I'm in Safari and invoke the quick-add window, I only want to add some data, click Return, and I want it to go away — I want the previous window (Safari) to be key and on top, not the main window of my app (unless of course the main window of my app was key before invoking quick-add).
So, how to close an NSWindow without activating the window below?
I can't figure this out. The only idea I had is that maybe you could make a helper application that would display this auxiliary window — but that sounds like a lot of work (sending data back and forth between processes, all that…). There must be a simpler way!
i don't think this can be (usefully) done with an NSWindow.
As in this answer, i would recommend trying to use an NSPanel with the style NSNonactivatingPanelMask instead of creating an NSWindow.
I'm trying to create a Master-Detail iPad application with a list of saved files in the Master view, and the main interface in the detail view. There will be many different views in the detail, however, and I would like to be able to use a tab bar so users can quickly move between detail views. Is it possible to create a tab bar to navigate just between the different detail views, and still keep the same master view? I could just put in a "main menu" type view, which would have buttons to get to all the different main interfaces, but I'd like to avoid doing that if I can.
Thanks!
Mike
From everything I've seen, this type of layout isn't possible, and isn't really consistent with what a split view should be used for. The more appropriate way to do this would be to use standard UIViews in a UITabBarController, then having the saved files as it's own view opened in a popover.
I have an application with a split view controller, at certain points, the entire screen needs to be replaced with a single window so that the split view controller and its menus no longer appear. (For example if you want to do full screen reading of a document)
What is the best way to either cover the screen or replace it with another uiview? Is it even possible?
This sounds like you want exactly what presentModalViewController:animated: will do for you. Does that not work?
I'm updating one of my Mac apps right now, and just discovered I need to place a SplitView behind all of my components. Is the only way to go about this the way I'm thinking? I need to move all components out of the current view and add a SplitView, then move everything back in?
The components must be placed inside the split view. Using the document window in Interface Builder might alleviate some of the burden.
There’s a handy shortcut in Interface Builder for this operation: the Layout > Embed Objects In menu item. For instance, if you have two views and want to create an split view based on them, select them both and choose Layout > Embed Objects In > Split View.
And in XCode 4.1: Editor > Embed In > Split View
I have a cocoa app with two types windows each of which requires a different main menu to be displayed.
In my MainMenu.xib I have the default MainMenu. In Window1.xib I have Window1 and in Window2.xib I have Window2 and it's MainMenu.
When I have the first Window open I have the default Menu, when I open Window2 I get it's menu.
However, when I switch back to Window1 I still see Window2's menu. How do I make the menu that is displayed follow the key window?
Generally, you shouldn't replace the entire main menu every time. It's more compliant with the Human Interface Guidelines to simply disable any menu items that don't apply to the current window. And if you really should have a completely different set of menus in the menu bar, maybe you should split that part of your application into a separate application.
NSApplication has a method, - (void)setMainMenu:(NSMenu *)aMenu. You can pass it a reference to the correct menu in the appropriate window controller, by implementing - (void)windowDidBecomeKey:(NSNotification *)notification.
Keep in mind it may be easier to change just the submenus instead of swapping out the entire main menu, since you won't have to maintain two different copies of the application, help, and other menus that won't change between the two windows.