For whatever reason, the font color of my debug console is a blue which makes it really difficult to read. I'm not sure if this is due to vs code settings or maybe project settings as, when I put a break point and evaluate expressions, the font color is a readable white. How can I change this output color to something more legible? See image below:
You need to change your setting in VS Code's setting.json. The required property is
{
"workbench.colorCustomizations":
{
"debugConsole.infoForeground": "#ffffff"
}
}
This setting will change the color to white. You can of course change it to any other color you would like to.
There are other properties as well, like debugConsole.errorForeground, debugConsole.warningForeground, etc. which you might want to change as well. All of these properties are inside workbench.colorCustomization
If you'd like to make use of full colour log output in the 'Debug Console' window then add the following property to your debugging spring profile:
spring.output.ansi.enabled=always
Alternatively, add it to your debug configuration vmArgs:
"vmArgs": [
"-Dspring.output.ansi.enabled=always"
]
Related
On Windows, once a Static control has been painted (it is already shown), how can we retrieve its text color ?
I have tried with GetTextColor(), GetDCPenColor() but they don't work.
thanks
GetSysColor(COLOR_BTNTEXT) or GetThemeColor if you are using Visual Styles. A subclassed control might change the default by handling WM_CTLCOLORSTATIC.
I am using VSCode and the (default) Light+ theme, on Windows 10. I like this theme but have a lot of trouble seeing the yellow against the white - same is true for all the "light" themes, so there is no point changing themes.
I have found workbench.colorCustomizations in Settings - specifically changing editorBracketHighlight.foreground1 , but it won't stay on the colour I have selected (dark blue) - it sometimes shows as blue (and not consistently) when I bring up the VSCode editor, but, even if I see blue initially, it switches back to yellow shortly after. There seem to be various ways to change the settings, but I haven't found one that will stay!
BTW I have specified editor.bracketPairColorization.enabled (and this does work, using the old colours), so this is not the problem...
Help would be appreciated! TIA
PS I don't care whether this is associated with my workbench or all projects, and all languages or each language specifically (I am just doing Go right now), as I would want this for all projects, and all languages...
To get a better idea of whats going on behind the scenes, first install the Scope Inspector
https://code.visualstudio.com/api/language-extensions/syntax-highlight-guide#scope-inspector
then open your settings.json with ctrl+shift+P -> "Preferences: Open Settings.json".
Now open a .go file that you want to use as a test subject... and then enable the scope inspector:
ctrl+shift+p -> Developer: Inspect Editor Tokens & Scopes
For me I am using a Slice tutorial as example, Light+ on MacOS :
moving around your cursor you will see different scopes are applied to different tokens in your code.
In this example the inspector shows that it has 2 scopes being applied.
To change the color, go to the Settings.json file...
Inside, alongside whatever else you may have added, put in the "editor.tokenColorCustomizations" object with a sub "textMateRules" object, and include the scopes you want to target using the ScopeInspector mentioned above:
{
"editor.tokenColorCustomizations":{
// "comments": "#33FFCC", //will affect all comments in VSCode...
"textMateRules": [
{ "scope": "punctuation.definition.bracket.square.go",
"settings": {
"foreground": "#8110239f",
"fontStyle": "bold",
}
},
//.... Other rules you may add for different scopes you find with inspector etc...
]
} //end "editor.tokenColorCustomizations"
}
In this example, The result immediately changes to a dark red:
It seems that I can now colour the brackets as desired without using testMateRules, as follows:
"editor.bracketPairColorization.enabled": true,
"editor.guides.bracketPairs": "active",
"bracket-pair-colorizer-2.forceUniqueOpeningColor": false,
"bracket-pair-colorizer-2.showVerticalScopeLine": true,
"bracket-pair-colorizer-2.showHorizontalScopeLine": true,
"bracket-pair-colorizer-2.colors": [
"#3344F0",
"Orchid",
"LightSkyBlue",
"Green"
],
This seems to work - maybe someone could let me know if there is a problem with this! Thanks
I would like to change line's parameters of data visualizer (I'm not sure is the data visualizer module) like in the following image :
I tried to change lineColor parameter of all visualizer module I've found in "IntegratedCanvasVisualizer.ned" but none has effect.
I'd like to set icons positions and size because when I zoom out all icons are "pulled up" resulting in this :
I had a look in the source code (NetworkNodeCanvasVisualization.cc), tried to change parameter (size, distance), none has effect.
How to hide node's name (e.g. host[4] in first image) ?
Thanks for support.
1.:
The red lines are OMNeT++'s (or, more precisely, Qtenv's) own built-in message visualizations. They are completely separate from the INET visualizers. Unfortunately, the thickness of these lines can't be changed at the moment.
Their color is determined by their (optional) DisplayStrings, see [1] and [2] for details. However, when the messages take their "line form", many of these tags, like the "shape", and "outline" are ignored.
If they have no color set in their DisplayStrings, Qtenv has an option to color the messages based on the value of their "kind" field [3].
If they are more in the way than they are useful, you can disable them globally in the Qtenv Preferences dialog, or you can disable message animations on a per-module basis, by setting the builtinAnimationsAllowed field to false.
2.:
I think you should submit this question separately in the INET bug tracker.
3.:
What #jerzy-d said. There is even a shortcut for this, Ctrl+L. Hiding the names of individual submodules is not possible right now.
Ad. 3. To hide names of modules right click on the network and deselect Show Module Names.
In AmCharts documentation,both ChartScrollbar and ChartScrollbarSettings have same properties and looks like they bring about the same feature for the stock chart.Any significant difference between them?
http://docs.amcharts.com/3/javascriptstockchart/ChartScrollbar
http://docs.amcharts.com/3/javascriptstockchart/ChartScrollbarSettings
Ok, so it seems like the ChartScrollbarSettings do not work like the other settings:In a StockChart a global scrollbar is added by default. It does not matter if you're using the ChartScrollbarSettings for settings properties, or not. It will be created unless you're using:
ChartScrollbarSettings: {
enabled: false
}
In the panels you can still add local scrollbars using ChartScrollbar (Panel control is AmSerial). They work only for the panel they're inside.
So, I am having an odd behavior. Maybe it's intentional, but I can't seem to figure it out. I haven't worked much in Blend and prior to this been mostly coding XAML manually. I am trying create a custom template for a MenuItem and when it's being moused over, I need to turn its background a specific color. So, I'm doing this MouseEnter event trigger on the OuterBorder. When I try to change the color, no matter what color I set it as, it turns black immediately. This happens on all of the control in template, regardless which one I choose. So, I have to manually go into XAML and change it to the specific color.
After I set it to a specific color within the XAML code, if I try to change it through the Properties menu, it'll turn back to that color I set in the code.
If I export template into a ResourceDictionary, it lets me edit everything as if nothing wrong is occurring, but when the template is applied, the default background of the MenuItem control turns black.
By the way, this is Blend for Visual Studio 2013.
Any ideas what's going on?
What I ended up doing was not creating a separate even trigger and instead edited the template's existent triggers. Which worked great. My only concern is that the default one did not do fill, so I fail to see how there was a conflict between the two. Not sure if anyone knows?
Figured it out. Silly me. I was trying to change background that didn't exist. So, it had to create the background for the storyboard, and thus was setting it as the default black. What I did was create a background and set it's opacity to 0% and then change that instead. Worked as intended.