Open WebStorm in Presentation Mode - view

Is it possible to open WebStorm in Presentation Mode from the very launch of the ide?
I mean before closing the ide, I am using a Presentation Mode, but once ide is closed and reopened the Presentation Mode is not preserved and I have to enable it manually again.
Thank you.

There is currently no way to launch WebStorm directly in presentation mode.
You could make a feature request to JetBrains and hope for the best.
Meanwhile, you can easily define a key binding to toggle presentation mode.

Related

Visual Studio 2019: Stop debugger when browser window is closed but do NOT close browser when debugging stops

If I close a browser running a web application, it is desirable that the debugging session dies. After all, this equals to closing a windows application. However, if I stop debugging and the browser has more than one tabs (as often is the case), all of them will close - definitely not what I intended. Not using this option means I continuously forget the debugger running and clicking the stop button is just extra work.
Is there an add-on to Visual Studio or any other trick that allows to do only the first: stop debugger when window is closed?
Who thought it would be a good idea to put two options behind a single checkbox? This is a double-edged sword at its sharpest!
It's not exactly what you want. But, it might be a workaround. If you enable JavaScript debugging in Tools->Options->Debugging and then you Debug->Detach All. The browser should stay open and debugging should stop... Now it would mean that the application is still running, which might not be desirable.
It's a great suggestion to make this an option. I'd encourage you to open a suggestion on developer community.
Tools Options:
Detach:

vs2019 external tool uncrustify hide console

I have been able to successfully add and configure uncrustify as an external tool to vs2019.
The problem I have is that the console window flashes each time uncrustify is executed (via keyboard shortcut).
Is there a way to hide the console window or prevent it from appearing?
Thank you all.
You can enable the Use Output window option for the tool.

Visual Studio 2013: How to send app to second monitor upon finishing build?

This question is solely about workflow in VS2013. In VS2012, when I would build my app, VS would display the app on the second monitor attached to my system. This was nice because I could see my IDE while I interacted with the app. However, in VS2013, the app always just displays over the IDE, so I have "move it out of the way" just to get back to the code. I would like VS2013 behavior to match that found in VS2012. Is there a setting in the IDE that I can switch on to ensure the app displays on the second monitor?
I did find another question on SO about this regarding VS2012, but the solution there does not work for Win8.1 using VS2013. Is there an option for this?
it's not exactly the answer to your question - garaber has already addressed that - but also useful in this context is that you can move a window to a different display using the keyboard -
windows-shift-left arrow
and
windows-shift-right arrow
fast, easy way to move a window to an adjacent display (either to the right or the left)
EDIT:
should have noted that this is not confined to visual studio - this is a feature introduced with windows 7 and works with any window.
Here's a couple of good links that will show you how to do what you're wanting:
Save and restore form position and size
Restoring window size and position with multiple monitors
You can also change your principal screen, and it works :
In, Screen Resolution : set your second screen as a principal screen.

Visual studio detect Ctrl+F5 and F5 mode?

Is there any way that I can understand that my code is running with Ctrl+F5 or F5?
I wrote a GUI for an application for some students but it doesn't work some time when run it with F5...I want too detect F5 and Ctrl+F5 mode to disable GUI when user run it with F5.
CTRL-F5 runs the application without the debugger attached. You can tell if it was started with plain F5 by checking the System.Diagnostics.Debugger.IsAttached.
If the GUI sometimes breaks when run with a debugger attached, it is likely because you use multithreading incorrectly to access UI properties in a thread other than the main UI thread.
You can use the System.Diagnostics.Debugger.IsAttached Property to tell if a debugger is attached or not, i assume that's what you mean.
Hope that helps
Paul

How can I stop losing all my IDE window position when pressing the start debugging button?

I use Visual Studio 2008. I haven't seen this behavior before and, as far as I know, I didn't change anything in the options.
When I press Start debugging all the possibly windows (watch 1 - 4), data sources, properties, registers (to be honest I have not even ever seen these windows before) appear in front of the code window and stay there after I stop the debugger.
Anyone has an idea what could be causing this ? (I am using CodeRush and Refactor for quite a while now)
When I close and restart visual studio all the windows are where they should be.
PS: Previously I have seen normal switching from normal to debug mode and back with some repositioning changes. That is the way it used to work. Now it is not. It has suddenly gone mad and when going to the debug mode it sometimes shows all possible IDE windows and sometimes not. When it does it no longer returns to the previous state. I cannot find this in the options anywhere.
Visual Studio remembers 2 sets of window layouts, normal mode and debugging mode. My solution is to arrange my normal windows exactly like I want them, then start debugging an application and once again arrange all of the windows the way I want, usually making it as similar to my normal layout as possible, then stopping the debugger and doing a File Exit so that VS saves my settings.
After doing that, it recalls my 2 different layouts each time.
I'm experiencing the same thing - whenever the debugger is running, switching focus back to the IDE immediately caused the debug panel to expand.
I ended up just pinning the debug panel so that it always appears when debugging, and just changing its height as needed.
To add to palehorse, another tip is Full Screen mode.

Resources