The "options" sub-tab of the fiddler "Composer" tab lets you tear off the Composer into a floating window. Question is how to put it back? I lost the floating window and now fiddler's composer is gone. I didn't find anything in the menus to restore fiddler or its GUI to factory defaults. I tried uninstalling and reinstalling fiddler, no-go; Then uninstalling, grepping the registry and blowing away all keys that had anything to do with fiddler and reinstalling -- no-go. The only thing that worked was paving the machine -- (which I had to do anyway -- I didn't do that just to solve this fiddler problem!)
The floated Details View can be returned to the docked state by closing it.
In your case, it sounds like the view may have gone off-screen. On Windows 7 with Fiddler 2.4.1.1, a floated Details View shows up in the taskbar as a distinct Fiddler window. Hovering over the Fiddler icon on the taskbar, moving the cursor over the Details View preview, right-clicking the Details View preview, selecting Maximize, and then pressing Alt-F4 returns the view to its docked state.
Obviously, flattening your box and reinstalling Fiddler is also a solution. ;)
Related
VS Code was docking devtools pane within the window before. Now, It opens a new window that increases back and forth. Is there any way to dock it back? I tried a few settings they did not work. Also, there is no dock icon as in Chrome.
This started with vscode v1.74 and is an electron bug. See The developer tools become a floating window.
There is a fix reported there. Disable the setting
Windows > Experimental > Windows Control Overlay: Enabled
You will be prompted to restart vscode and then opening the Dev Tools will be docked as before. Apparently, the Electron bug has been fixed.
In the devtools panel, click the vertically-aligned three dots at the top right. That will open up a context menu. You will see a "Dock side" entry with different icons signifying option values for that setting. You probably accidentally clicked the one that makes it pop the devtools out into its own window. Select whichever option you actually want there.
Earlier The Panel of vscode used to close when I killed the terminal. But after I reset my pc and reinstall vscode, this is not happening. I after killing all the terminals I have to click on the "Close Panel" Button to close it.
How can I close the panel automatically on killing the last terminal?
Thanks for help in advance.
So the lower panel (or right/left panel if you moved it) should always automatically close if the terminal-view has had all of its terminals closed.
Now, with the above said, their is one exception, which is a common exception: When you show there panel with a view — i.e. the problems view, output-logger, etc... — with the terminal-view, the behavior of the panel changes. In the context I just described, the panel will not automatically close.
To solve the issue, remove all other views that share the panel with the terminal view. Then you should find that you get the expected behavior.
FYI, this has worked this way for a long time, and a while back (2+ years ago) there was a somewhat supported feature request to make the closing behavior of the panel more configurable — e.g. like adding settings that close the panel when the terminal-view has no terminals open, even if it is in a shared panel — however, I checked all settings & release notes and GitHub before answering this, and it appears that the panel & terminal view, in the context of this question, still behave the way that they always have since the first newer release of the non-beta VS Code.
Anyone know of a way to open Chrome Dev tools to a new window upon open?
I know that I can click F12 and then click the 'customize' button and change orientation or pop out the dev tools window. But that's an extra step, and often a window resize is necessary, and when you do it 50 times a day, it gets to be tedious.
Also, sometimes, on pages I'm testing, pressing F12 will change the layout of the elements on the page and even popping out the dev tools leaves the page layout different than before I opened dev tools. This can make it hard to tell if an element is visible or not, which makes troubleshooting Webdriver more difficult.
Ideally, CTRL+F12 or something to open dev tools as a separate window would be super handy. (to any Chromium devs that might be listening ;) But if anyone has another solution, I'd love to hear it.
If you have your DevTools un-docked, the dock mode, size and position of your DevTools window will remain the same as you previously set it. For example, I just set mine to be maximised on my other monitor. Every time I open up DevTools, it's an un-docked, maximised window, and there's no change to the layout of the inspected window other than the fact it's no longer in focus.
You could alternatively launch Chrome using the --auto-open-devtools-for-tabs flag, which will automatically open DevTools in the dock mode, size and position you had it previously. You can use:
Mac:/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --auto-open-devtools-for-tabs
Windows: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --auto-open-devtools-for-tabs
In WebDriver, you can set flags for how Chrome opens. However, after looking into this further, it turns out Chrome currently do not support multiple clients connected to the protocol simultaneously.
As for speeding things up, you can switch between dock positions with Cmd+Shift+D (Mac) or Ctrl+Shift+D (Windows). This toggles between the last two modes you have used, so say you have it docked at the bottom, you then pop it out, using the shortcut now will toggle between the two.
Here's how you do it. On opening the developer tools, with the developer tools window in focus, press F1. This will open a settings page. Check the "Auto-open DevTools for popups".
Originally documented here -- https://newbedev.com/automatically-open-chrome-developer-tools-when-new-tab-new-window-is-opened.
When I work with eclipse, I like to have my Java editor maximized, and all other views minimized in the trim stack (the area around the edges of the window). This way, I can expand the view only when I need it, by clicking on the view icon.
In previous Eclipse versions, when I finished working with a view, I clicked on another view or the editor so that it lost focus, and that caused it to minimize again. In Juno, it doesn't work - when I click on the editor, the view stays open and is hiding my code. In order to close it, I have to either click the view icon, or click on another program and then return to Eclipse.
Do you have any idea if there is a setting I can change to get the old behavior back?
Thanks!
Edit: Seems like a bug in eclipse.
I am unable to reproduce this problem using Juno SR1. Bug 371598 was fixed and looks like the same problem.
I am using Eclipse Juno. I was working in Java perspective and suddenly I minimized the console. I don't know where it went but I am unable to get it back. I even tried to get it from Windows>Show View>Console but I didn't get my console back.
It happened the same thing to me. Just click Window->Reset Perspective and everything will be back as it was when you installed eclipse.
Sure you'll have to customize it back to how you like it, but at least you'll have the console back.
If console is not visible, just search for "Console" in QuickAccess box on the right hand top of menu bar. you can get it back!
Stupid Eclipse. Are there no interface designers volunteering on this project? Why minimize something and make it hard to see where to bring it back? Probably all you have to do is hit Shift-Control-Tab-F9 with one hand while right-double-clicking the lower left hand corner. Hmm, how about a popup when you click a minimized Console that says "We see you've minimized your Console and you are clearly trying to switch to it. Would you like us to restore that so you can actually see it?" followed by "Are you really sure? Cuz ya know, you may be using this click path by accident."
The reset perspective works. Also, you can "Save Perspective" so it's not so hard to go back to your preferred Perspective.
Thanks for the tip.
Bring console to the front from Window -> Show View -> Console. Apparently the console remains invisible (that was the issue indeed), but it is virtually active in the foreground.
Close the current view (i.e. the invisible console) by going to the "Quick Access" box at the toolbar, typing "Close Part", and selecting the respective option on the drop-down.
Reopen console form Window -> Show View -> Console and voilà, it will appear. Drag it to your preferred location on the workbench.
This works for me under the following situation:
I had been previously playing with detaching several views (console included) and editors to a separate window on a different monitor; I have updated my workspace from Neon to Oxygen and I have had a hard reset at my computer. (So, not sure which among those was the reason that made it go wrong).
I wanted to avoid resetting my perspective, as it is highly customised, so I discarded that solution.
Other solutions herein proposed had not worked.
The console was working and the view became visible if I chose a different perspective (e.g. Debug) or a duplicate Eclipse window (which effectively provides a duplicate of a factory-reset perspective).
you could click the small icon on the bottom left and choose console. it will appear.