Opacity
Nichole Wernett
A in the range 0.0 to 1.0, inclusive, or a in the range 0% to 100%, inclusive, representing the opacity of the channel (that is, the value of its alpha channel). Any value outside the interval, though valid, is clamped to the nearest limit in the range.
opacity applies to the element as a whole, including its contents, even though the value is not inherited by child elements. Thus, the element and its children all have the same opacity relative to the element's background, even if they have different opacities relative to one another.
If text opacity is adjusted, it is important to ensure that the contrast ratio between the color of the text and the background the text is placed over is high enough that people experiencing low vision conditions will be able to read the content of the page.
Color contrast ratio is determined by comparing the luminosity of the opacity-adjusted text and background color values. In order to meet current Web Content Accessibility Guidelines (WCAG), a ratio of 4.5:1 is required for text content and 3:1 for larger text such as headings. Large text is defined as 18.66px and bold or larger, or 24px or larger.
I'm trying to represent the absolute density of a 2-variable scalar function by color and tranparency/opacity. By absolute denstiy, I mean the absolute function value. I tried to do the coloring as follows, but don't know how to give one color for positive values and the other for negative values. The following plot has automatically scaled color and looks okay, only because the function is symmetrical.
What I want to do further is to add opacity based on the absolute value. When the density function has low absolute value (whether positve or negative) in some region, then the region must be transparent relatively more than regions that have higer absolute value. And completely transparent when absolute value is 0. I tried using OpacityFunction but that didn't work.
I think one could color positive and negative regions with dintinct colors (monotonically, without concerning values), then add absolute opacity. That will consequently make regions with lower value less intense. Ultimately, I want to Blend such plots.
In addition to overallopacity, which affects layer styles and blending modes applied toa layer, you can specify fill opacity. Fill opacity affects onlypixels, shapes, or text on a layer without affecting the opacityof layer effects such as drop shadows.
Currently we have keyboard shortcuts for opacity in steps of 10 (10 to 100) using the number keys (or shift + number keys, depending on your settings) which is super useful but there is no shortcut for 0 opacity, I would find this very handy!
Is there a way to disable the opacity shortcut when using the number keys (1-9)?
I use Affinity software for digital painting and illustration, and I keep accidentally hitting '3' instead of 'E' for the eraser and changing my brush opacity to 30% by mistake.
I've also assigned Cmd+1 and Cmd+2 to rotate my canvas left and right, but the same problem here - I keep accidentally changing my brush opacity in the process if I don't perfectly press Cmd together with the number key.
I don't use the number keys to set opacity of my brush anyway, so I would love to disable and/or customise those shortcuts to accommodate my workflow better, but I can't seem to find those keys anywhere in the Keyboard Shortcuts panel. I wouldn't recommend removing this shortcut for those who use it, but perhaps having the option to customise it would be helpful?
This probably has something to do with them not being ordinary 'one press' shortcuts, since for example pressing 4 quickly followed by 3 sets opacity to 43%, so in effect there are 100 different keyboard shortcut opacity settings, including the 0 & 0 pair that sets opacity to 100%.
They are context sensitive, so like in the screen capture @Pšenda posted, if no brush is selected, they change the currently selected layer's opacity (which can be seen in the Layers panel) & if one is they change the opacity of the brush (which can be seen in the Context toolbar).
As I mentioned earlier, the opacity shortcuts built into the Affinity apps are not regular ones that are limited to pressing just one of the 10 number keys. They also accept quick sequences of 2 number key presses, effectively the same as having 100 different shortcut keys (!!!) on the keyboard to set opacity.
I'm three years late, but I'd also LOVE to be able to change this behavior. Same as "armada", I'd love to use 1 & 2 as my zoom in and zoom out shortcuts (instead of F15 F16 or CMD+-), but I'm stock with the layer/brush opacity behavior. UNLESS... I miss something/it has been update?
Ok, it's unfortunate. Is there a way to deactivated those shortcuts altogether (numeric keys affecting layers & brushes opacity)?
It's driving me nuts as I am accidently hitting them (another software I use too often as put 1 & 2 in my brain forever)
Opacity is applied from parent elements on down the element tree to child elements, but the visible effects of the nested opacity settings aren't indicated in the property value of individual child elements. For instance, if a list has a 50% (0.5) opacity and one of its list items has its own opacity set to 20% (0.2), the net visible opacity for that list item will be rendered as if it were 10% (0.1), but the property value of the list item Opacity property would still be 0.2 when queried.
Even if the declared or evaluated opacity is 0, an element still participates in input events and commands, and is potentially focusable. This aspect can be useful, for instance you can use an opacity-zero object (such as a shape) for masking underlying objects with transparent elements. The opacity-zero object can then handle all the input event processing for an underlying area. However, the Background or Fill of the object or shape should be set to a value, even if it is Transparent, otherwise hit testing is not enabled, and no events are received.
So, does this work in the app, just not in the printout? I had an issue with opacity before with a unique value renderer - the API didn't like how I was constructing the renderer... let me see if I can dig that up.
I would look at the renderer/selection symbol, if you haven't already - I posted a thread earlier where I ran into opacity issues... it's possible you may be experiencing a similar scenario. Is it at all possible for you to create a jsfiddle demonstrating the issue?
You can also use variant modifiers to target media queries like responsive breakpoints, dark mode, prefers-reduced-motion, and more. For example, use md:opacity-100 to apply the opacity-100 utility at only medium screen sizes and above.
It has been answered why they didn't want you to use true black and instead lowering the opacity to create shades of gray. So natuarally they would choose these values out of their "Gray" color palette.EDIT: I see there's no references for why not to use true black, here's a UX.SE answer explaining Is there a problem with using black text on white backgrounds? If you scroll through the answers there are a bunch of (not very academic but generally accepted) sources.
I've never really thought about it this way, but it's a really neat approach. The designer is no longer guessing at what the appropriate "Second level" colour is for #000000. Is it #ccc? #7a7979? ... don't have to guess anymore. just set opacity.
On some displays, full black (#000000) could fail to render properly.Setting a small opacity helps to give a sharper and better overall appearance to the text. Even tho this problem is almost gone nowadays, I believe that's the idea behind the .87 opacity on the Material Guidelines.
How do I correctly set the opacity to semi-transparent (e.g., opacity=0.2) in a node with a drop shadow?It seems that with the "naive" approach the shadow shows up through the semitransparent filling, which somehow makes sense.
hence pic ["$\alpha$" opacity=1,draw=orange,fill=orange!50,fill opacity=0.5,angle radius=1cm] angle=a--b--c gives you the desired effect. Note no comma after " ... ". The braces aren't needed in this specific case because there is only one option, opacity.
I have created these button images. I am trying to make it so that when the user hovers over the image, the img element opacity changes while the elements on top like the span and the h2 elements stay completely opaque(visible). I targeted the img element specifically on hover in my css to do just that but for some reason the opacity of all the elements change. Why is this happening? What am I doing wrong and how can I fix this? The code follows.
For example, say I create a new layer, change my brush to solid black, but to 50% opacity, then draw some artwork. Then after the artwork is drawn, I realize it's too light and want to increase (darken) the artwork's to say 75% (so it's darker), or 100% (so actually appears solid black). How can this be done? Just to be extra clear, the color is solid black, it only appears grey (or lighter) because of the 50% brush opacity (layer opacity is 100%). Here are the methods I've tried so far:
aa06259810