(Related question to "Matching windows system colors: light on dark".)
There doesn't seem to be an "official" background color for COLOR_GRAYTEXT. This looks strange to me. Do you know any?
Assuming grayed out things can somehow be enabled, one would guess that both COLOR_3DFACE and the (tabbed) dialog texture will look ok
Related
Maybe a simple question, but I am trying to enable light/dark mode for my Mac app. I added a color set, but what appeared wasn't what I expected. Instead of three colors I just have two, Any and Dark appearance.
I tried looking around for a fix, but I wasn't able to find anyone talking about this. Does anyone know what's going on?
Here's a screenshot I took that shows what is happening.
Occam's razor. You don't need three! Any plus Dark means that if you give Dark a different value, Any applies only to Light.
I am using the Three-choice Button component in xamarin, but I don't know of a way to change the button color. The font and shadow ect can be changed, but I would like to change the grey color.
Can anyone provide some insight on how to do this?
I solved this a different way. I am using a normal ios switch, and just changing the background colour of the switch, ie Green, Grey or Orange.
Not exactly the answer to my question, but looks neater than the component did.
I'm making a completely custom control (NSView), and I want to use the user's preferred highlight color for part of it when it's selected, like NSTableView does.
Unfortunately, there doesn't seem to be any way to get this. The NSColor documentation only lists one (non-deprecated) user-chosen color, selectedTextBackgroundColor, and NSTableView uses a much darker or more saturated (?) color for the selection highlight.
I've tried a couple things, like turning up the saturation (fails for gray), and darkening with shadow() (looks bad, and not like NSTableView), but I'm not an expert on colors.
Does anybody know what NSTableView is doing, to get this color? Is there any way to access it more directly?
NSColor.alternateSelectedControlColor is what you want. The comments in NSTableView.h are somewhat out of date (referring to the color being light blue, when it isn't any more). I don't see the constants in NSColor being deprecated... not sure what you are talking about? (Maybe a documentation bug? When in doubt, look at the headers...)
Ok. I am finding it difficult to visually discern where the current focus of my editor is. The image below shows that I am currently in the bottom PathIcon tag while the top PathIcon tag is highlighted because it is a matching type. The similarity in color has finally driven me crazy.
Does anyone know the correct text-type in the Fonts and Colors dialog of Visual Studio 2015 to change this color? And, look, for all the StackOverflow haters trolling the board, please resist closing this q until there is an answer. Then you can have your fun.
It looks like there are actually two different colors in play here. The grey box on the "<PathIcon" that contains the cursor is "Brace Matching (Rectangle)". The purplish box on the other "PathIcon" looks like it is the background portion of the "Match color", which is installed by the pro power tools.
The latter color won't reset if you change the color in fonts and colors but will be correct for editor instances you open after changing the color.
I think you're looking for Highlight Current Line (Active), which controls the colors of the line your cursor is on.
For some reason the selected tab on TextMate is almost un-noticeable, I really cannot make it out, they all look the same to me. When I switch tab I notice it changing color, so I guess it's very very very slightly different, but that doesn't help much.
I've been having this problem for a while, but IIRC it worked fine some times ago — I've no idea what happened to trigger this change.
TextMate 1.5.10, OSX 10.6.8
Any idea?
Your screenshot looks normal to me.
Check your monitor’s “brightness” and “contrast” settings, and possibly your color profile (System Preferences → Displays → Color). On a flat-panel display, there may be a setting which will over-brighten the input signal, causing the top end of the range (light gray to white) to be clipped, so that it is all white (just like overexposure in a camera). There is no good reason to do this ordinarily, especially with a digital input signal, so you should adjust the settings to avoid clipping.
Here’s an image of a black-to-white gradient with a gray border. If a large portion of the left end looks flat white, then you are having that problem.