I am trying to get a permanent view of breakpoints (or at least lasting until I remove it) docked next to the Debugger panel. E.g. I would like it to take place of Watches, since I do not use watches much. Currently, viewing breakpoints is done by clicking the small double circle icon in the Debugger but that pops a new large window that occupies most of the screen. I would like a small and permanent view of breakpoints (just like the one in Eclipse).
If you open up the Favorites tool window (Alt+2) you will see the breakpoints.
You cannot put this window inside the Debug tool window but you can have it docked above or beneath (or anywhere you want).
Like this:
Or like this:
The last image shows the Debug window docked with the Split Mode Off while the Favorites window has Split Mode On
CTRL + SHIFT + F8 works for me
IDEA 2017.1.3 allows breakpoints to be edited (e.g enabled/disabled) from the Favourites window (right click, Edit breakpoint).
Related
In the Intellij Settings I activated Editor > General > Show quick documentation on mouse move and I like it. But when there is a warning message also shown as popup when the mouse hovers over, then the documentation popup just hides the warning like this:
Well, that's not nice. Is there a way to solve that?
The are a couple of alternatives to displaying the quick documentation as a popup:
Display the quick documentation in a separate panel.
Display the quick documentation in a floating window.
To display the quick documentation in a separate panel:
Position the mouse so that the quick documentation popup is displayed.
Click the Options icon in the bottom right of the popup.
Select Open as a Tool Window from the drop down menu.
After doing that the quick documentation popup is displayed in a panel on the right. It is still automatically updated as you move the mouse.
Alternatively, to display the quick documentation as a floating window:
Click the Options icon in the top right corner of the panel.
Select Windowed Mode from the drop down menu.
After doing that the quick documentation is shown as a floating window which you can position wherever you want. You could even place it on another screen if you have multiple screens. Again the content is still automatically updated as you move the mouse.
Select Open as a Popup from the Options drop down menu on the panel or the floating window (or press CTL/Q) to revert to using a popup for the quick documentation.
The best choice is a matter of personal taste, but both of those approaches would solve your overlapping popups problem.
Update:
The previous screen shots were produced using IDEA Ultimate 2018.1 EAP. With Ultimate 2017.3 it seems that the situation is slightly different. After clicking the Options icon, only a control to adjust the font is shown. In that case click the Pin icon in the top right of the window:
After doing that click the Options icon in the top right of the window to see the menu options:
how can we dock the java-doc window to the IntelliJ IDE?
There is no Docked mode in the window-popup like explained in the IDE help
e.g. it should be like the Structure, Messages, Version Control tool Window.
Yes, there is something wrong with this window: by default it shows up in your face, preventing you from getting any work done, and it is not immediately obvious how to dismiss it. A programmer's first encounter with this window tends to be a rather bad user experience.
The way I dismiss it is as follows:
Click on the gray gear menu (the one at the top, not the blue one right below it)
Uncheck Floating mode. It will then obtain a "Docked Mode" option.
Move it to any side you like; it will then stay there.
I want the user to be able to click an existing panel and drag it out of the application to make a separate window they can work in. How can I accomplish this using wxWidgets?
You may want to look at the built-in way to do this, known as wxAUI.
If you absolutely need to do it yourself, you will need to create your own top level window overlapping the panel when it starts to be dragged and then reparent the panel under this window.
I want to have an icon in the menubar in my Mac app - and the icon should spawn a menu upon clicking. While having more entries in the menu, I would like to have a top row as a universal text entry field - like it is in Spotlight:
http://dl.dropbox.com/u/3943878/_mine/Screen%20shot%202011-07-16%20at%2012.29.18.png
Is it possible to add such a field to NSMenu? Or should I do it as a panel-type window?
If you're using xcode 4 , make a custom view in interface builder and add a textfield or anything you want to it. In IB also drag and drop a "Menu" from the objects library with as many items as you want in it. Then simply ctrl+click the menu item you want to make into the text field (In your case it would be the top one) and drag to the custom view and select "view". Now when you open the menu, instead of showing a menu item in that space, it shows whatever was in your custom view.
EDIT: As for your comment here's what you should do. Make your menu an outlet by opening the assistant editor view and ctrl+click from your menu to the header file that you want to use. now, simply make a method that will run whenever the menu will open, conveniently apple already made this, it's called menuWillOpen.
- (void)menuWillOpen: nameOfYourMenu{
[self performSelector:#selector(methodExecutedWhenMenuIsClicked) withObject:nil afterDelay:0.0 inModes:[NSArray arrayWithObject:NSRunLoopCommonModes]];
the delay at 0 will make it happen immediately, it must be done in the common modes run loop so that the menu will be updated even while it's open. Now just make the methodExecutedWhenMenuIsClicked and set it so the text field responds.
- (void)methodExecutedWhenMenuIsClicked{
[[yourTextfiled window] makeFirstResponder:yourTextField];
You can put any view in a menu using -[NSMenuItem setView:]. See the long comment in NSMenuItem.h and the section Views in Menus in Application Menu and Pop-up List Programming Topics.
You're probably going to struggle quite a bit. I just tried doing the same thing, and reading the Views in Menus in Application Menu and Pop-up List Programming Topics document referenced by Ahruman, I found this:
A view in a menu item can receive all mouse events as normal, but keyboard events are not supported. During “non-sticky” menu tracking (that is, manipulating menus with the mouse button held down), a view in a menu item receives mouseDragged: events.
I think we're SOL. Apparently Spotlight pops up a borderless window instead.
I have a window that is set with NSBorderlessWindowMask, and also kCGDesktopWindowLevel. When a NSPanel is supposed to appear from say the selection of a Dock Icon menu or a Status Bar Item menu, the NSPanel will not display if the application is not the front most window.
So this program at this time only has a Status Menu Item (think how QuickSilver is implemented) and when I choose Preferences from my menu it is set to show the Preferences Panel by using Makekeyandorderfront, however unless you have just launched the application and done nothing else, when you select Preferences nothing happens.
I have found that when I choose my menu item for Sparkle's Check for Updates, that the check for update panel will appear and then my preference panel which I told to open will appear.
So it seems like makekeyandorderfront is not really bringing it to the front, perhaps.
Does anyone know how to fix this?
Should I call something besides makekeyandorderfront, or maybe something in conjunction with it?
Thanks in advance
Panels are designed by default to work this way. They're designed as auxiliary windows for your application and always disappear when the application deactivates. You will probably also run into issues with the panel becoming key... but to cure your disappearing panel issue, send this message to your panel:
[panelObject setHidesOnDeactivate:NO];
You should probably be using actual NSWindow objects here instead of NSPanel objects, but since I don't know much about how your application works, you'll have to look into that yourself. For more information on the difference between panels and windows, please review the documentation here: Window Programming Guide