I'm now converting the hex number, but that isn't telling me what the opacity is. I thought this was confusing the first time I saw it, but comparing it to the String.Format() method brings it home for me. Luckily, we have a bit of PowerShell magic to shorten this for us. Here, we're specifying a string format that renders the first parameter as hex as well as the number we're converting. NET, our first guess might be to just convert it to PowerShell, like we did before. To go the other way, we'll tap into standard string formatting logic. So, to convert my hex number to decimal, I was able to drastically shorten the code (can you even call this "code?"). For hexadecimal numbers, you can reference a value without treating it as a string by prefixing it with 0x. Also note that, for some classes, you may need to use the fully-qualified class name, which includes the namespace.Īfter doing this, I remembered the numeric format shortcuts available in C#. First, you have to surround the class name with brackets () and, second, you have to separate the class and method names with two semicolons (::). 2 for binary, 8 for octal, 10 for decimal, and 16 for hexadecimal).From a PowerShell perspective, there are a two more things to note here, since we're accessing a static method. The first parameter is the value to convert and the second value is the base (i.e. To go the other way, you simply switch out the method name and first parameter you pass in. NET developer, I knew the Convert class has the ability to convert to/from hex, so I started out with this simple one-liner to convert a hex number to its decimal equivalent. All that aside, I found myself wanting to find out what a certain opacity was when working on a WPF app, so instead of opening the calculator, I referred to my handy-dandy PowerShell, which is always open on my desktop.īeing a. I will say that this is perhaps worsened by WPF and Silverlight, which have incorporated opacity using the RGBA (red-green-blue-alpha) spec, which is arguably a misnomer, since the alpha channel (aka opacity or transparency) is specified first. I'm sure graphic artists deal with this a lot, because I know I find it relatively annoying when I've used apps in the past that only accepted 3 decimal numbers instead of the RGB hex format. I can't tell you how many times over the years I've opened the calculator to convert to/from hex values to either get a specific value or find out what percentage is being used. If you're doing any web or WPF/Silverlight work, you're probably used to dealing with the RGB (red-green-blue) hex color format.
0 kommentar(er)
