How do I turn off the sound signal? - ndepend

When an error occurs,NDepend beeps.
When the project has errors.
How do I turn off the sound signal?
Update-1
I use:
Visual NDepend.
The event at which the sound signal appeared:
I performed the close project action.
File -> Close Project.
There was some kind of malfunction in the project.
Therefore, a beep sounded and a dialog box appeared.
Window content: Probably suggested saving something.
Update-2
Created the NDepend project.
Added a project for analysis.
Clicked: File -> Close Project.
NDepend - performed a beep and displayed a window with a suggestion to save the project NDepend.

Since NDepend v2022.2.1 released 10th of November 2022 there is a new Miscellaneous option panel that contains the disable sound required setting:

Related

Adding audible alert for breakpoints in VS Code 1.52.1?

I'm aware of the following question and answers:
Visual Studio: How to trigger an alarm when a breakpoint is hit?
However, none of the solutions seem to work for me. I'm on Windows 10, with Visual Studio Code 1.52.1. When I go to the Windows sound settings, there is no Visual Studio section, so I can't set it there. The "ding" extension is no longer supported. The macro option also does not seem possible in my version of VS.
Does anyone know of any alternative solutions? I'm running code that takes sometimes 30+ minutes, so I would really benefit from an audible alert so I can immediately get back to work when it completes.
In the Insiders Build v1.65 there a few new individual settings controlling audio and it appears that the general Audio Cues: Enabled has been removed in favor of the more specific settings.
audioCues.onDebugBreak: Plays a sound when the debugger stopped on a breakpoint.
audioCues.lineHasBreakpoint: "Plays a sound when the active line has a breakpoint."
audioCues.lineHasInlineSuggestion: "Plays a sound when the active line has an inline suggestion."
audioCues.lineHasError: "Plays a sound when the active line has an error."
audioCues.lineHasFoldedArea: "Plays a sound when the active line has a folded area that can be unfolded."
audioCues.lineHasWarning: "Plays a sound when the active line has a warning." (off by default)
And see https://stackoverflow.com/a/70988028/836330 for how to list, hear and modify these settings using the
Help: List Audio Cues command from the Command Palette.
This is in the Stable Build v1.64 now.
Setting: Audio Cues: Enabled
auto : default - Enable audio cues when a screen reader is attached
on : Enable audio cues
off : Disable audio cues
This works for breakpoints.
I suggested the feature on GitHub a while ago and they actually implemented it in vs code insiders January build.
My github issue
VS Code Insiders

How to disable annoying build error notification when using project generated from pnp spfx generator

I have created a project using the pnp/spfx Yeoman generator (https://github.com/pnp/generator-spfx), and now I get a Build Failed" notification that pops up in the lower right-hand corner of my VS Code window along with a beep every time I save a file and there are errors anywhere.
I would like to turn this off somehow. I have looked everywhere and I have not been able to figure out what is triggering this notification, or how I could go about turning it off.
I was hoping someone on here that has experience using this generator and could point me in the right direction.
This is what the notification looks like:
As you can see there is no way to click on the notification to configure to turn it off or anything. No Right click options either.
Just faced the same annoying issue. You can turn off the toast in the gulpfile.js. Add the following:
build.mergeConfig({
showToast: false
});

Evaluate live javascript edits in Chrome?

How do I tell the Chrome developer tools that I'm done live-editing a section of javascript, and want the result to be "evaluated"?
Editing the javascript on the fly is simple, I simply put the cursor somewhere in a script in the Scripts tab and start typing, but how do I finish the editing process?
I read here that "changes you apply to the code are expressed only at the time when execution passes through them", but even if I try editing a function when it's being called (i.e., when having a hit breakpoint inside it), I can't get my changes to be acknowledged. Edit: this whole, "execution passes through it" stuff seems false or out of date at best.
Editing javascript on the fly in the developer tools is demoed by Paul Irish in this video around 3:30, but I can't figure out how he goes from editing code, to having it actually be used by the browser.
Ctrl+S or "right-click > Save".
Make sure you haven't enabled pretty-print, as you can't live-edit code, then.
This is what you are looking for:
1.- Navigate to the Source tab and open the javascript file
2.- Edit the file, right-click it and a menu will appear: click Save and save it locally.
In order to view the diff or revert your changes, right-click and select the option Local Modifications... from the menu. You will see your changes diff with respect to the original file if you expand the timestamp shown.
More detailed info here: http://www.sitepoint.com/edit-source-files-in-chrome/
Go to sources, choose the file you want.
Click the pause button to pause debugging .
Modify the script adding a console.log or whatever you want, wherever you want
Save the file (cmd-s or ctrl-2)
Click the pause/resume button to resume execution
the modified code will be executed

Modifying Running Code in Xcode Fix (found in the 'Run' menu)

I am attempting to use the 'Fix' command found in the 'Run' menu in Xcode to modify my running code without having to rebuild. I have read apple's documentation on it but following their
'typical fix-and-continue workflow:' (http://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/XcodeDebugging/230-Modifying_Running_Code/modifying_running_code.html) doesn't seem to be working for me...
Here is what i am doing (from scratch):
- create view-based project in Xcode
- create click event to trigger a function that just logs some output
- run in simulator with debugger (command-Y)
- click 'pause' in the debugger.
- add another log (or some other simple change) to the function
- save modified code
- select 'Fix' from the 'Run' menu
- click continue and click button
The added log doesn't appear...
Not an answer, per se, but this "Fix and continue" system is disappearing in XCode 4. I wouldn't invest a lot of time in learning to use it, or developing a debugging strategy around it.

Any way to stop Eclipse CDT build?

I'm attempting to build a project in Eclipse CDT and the build process fails early on, but then takes minutes to finish computing and finally quit.
How, through the Eclipse IDE, can I stop the build process.
I know there must be some way because I can delete any random file from the Project Explorer and a box pops up with the processes and I can click the red box next to build and it quits. But I shouldn't be required to delete a random file to get that box to pop up. Where is it?
There is a "progress view" found at Windows->Show View->other->General->Progress. That has the little red square I need to stop any particular task.
FYI - there's also a setting in the Properties sheet to "Stop on first build error".
Under the C/C++ Build item in the Properties page, click on the configuration you wish to modify, choose the Behavior tab, and click the checkbox under "Build Settings" ("Stop on first build error").
You can still use John's method to stop the build at any time, but if you're looking to have the build stop when you first encounter an error instead of continuing on, this setting might be helpful.
I use -Wfatal-errors flag in Makefile in Eclipse to prevent polluting my console
-Wfatal-errors
This option causes the compiler to abort compilation on the first error occurred rather than trying to keep going and printing further
error messages.
https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Warning-Options.html
You can disable the console's annoying focus-stealing behavior both for the build messages (so you can get the progress dialog to stay open) and for your program's console output (when debugging multiple threads). Go to window->preferences->C/C++/Build/Console and you'll find an option "Bring console to top when building (if present)". Uncheck that and you then can pause the build as you wish. To keep your program output chilled you can go here: http://georgik.sinusgear.com/2011/12/22/how-to-disable-stealing-of-focus-by-console-in-eclipse/