Converting hex Numbers to Decimal

[mgardner323]

I want to convert hex numbers to Decimal numbers can someone give me an example on how to do this:

I have it read a MUL for the gumps and it reads everything into as a hex number after I place the gump i can tell it to show the script pretty much and I need to convert the hex number to Decimal. heres what happens when you have it show the script:

public override string ToString()
{
return "GumpPic "+Convert.ToString(ID,16).ToUpper()+" "+_x+" "+_y;
}

[Ravatar]

        public static int ConvertHexToDecimal(string hexNumber)
        {
            if (hexNumber.IndexOf("0x") != -1)
                hexNumber = hexNumber.Substring(2, hexNumber.Length - 2);

            return Int32.Parse(hexNumber, System.Globalization.NumberStyles.AllowHexSpecifier);
        }

[punt59]

Originally Posted by Ravatar

        public static int ConvertHexToDecimal(string hexNumber)
        {
            if (hexNumber.IndexOf("0x") != -1)
                hexNumber = hexNumber.Substring(2, hexNumber.Length - 2);

            return Int32.Parse(hexNumber, System.Globalization.NumberStyles.AllowHexSpecifier);
        }

Not a biggie, but the above code snippet I believe makes two assumptions (I do not profess to be versed in C#).
1. That the 0x occurs at the very beggining of the string. That there is no other whitespace in the string leading up to it. To address, one would adjust the Substring() call to use the index returned by the IndexOf() call.
2. It also assumes that one will never enter 0X instead of 0x.

These assumptions are probably valid 99% of the time, so I am sure one is probably making fine making these assumptions.

[Ravatar]

Originally Posted by punt59

Not a biggie, but the above code snippet I believe makes two assumptions (I do not profess to be versed in C#).
1. That the 0x occurs at the very beggining of the string. That there is no other whitespace in the string leading up to it. To address, one would adjust the Substring() call to use the index returned by the IndexOf() call.
2. It also assumes that one will never enter 0X instead of 0x.

These assumptions are probably valid 99% of the time, so I am sure one is probably making fine making these assumptions.

Well... if you were working with data that you could not verify as being valid ahead of time..

        public static int ConvertHexToDecimal(string hexNumber)
        {
            hexNumber = hexNumber.Trim().ToLower();

            int intStart = hexNumber.IndexOf("0x");

            if (intStart > -1)
            {
                intStart += 2;
                hexNumber = hexNumber.Substring(intStart, hexNumber.Length - intStart);
            }

            return Int32.Parse(hexNumber, System.Globalization.NumberStyles.AllowHexSpecifier);
        }

That is a little less trusting of the input. It worked with the following cases:

Pre-Conversion:  "0X411901"
Post-Conversion: 4266241

Pre-Conversion:  " 0x7F00FF00"
Post-Conversion: 2130771712

Pre-Conversion:  "sometext   0X04"
Post-Conversion: 4

Pre-Conversion:  "     0x12345678"
Post-Conversion: 305419896

If anyone tries to pass something even worse through this method, they're probably better off receiving an exception.

[punt59]

Hmm, I thought 0x and 0X where both valid (at least in most of my C++ data reading days). One can never tell what a user will do.

Never knew it wasn't technically valid! Good to know. Thanks for that tidbit!

A word of caution though, if deaing with user generated data, one may run into it.

[Ravatar]

Well, I coulda swore in Visual Studio 7 it would refuse "0X...", however Visual Studio 8 seems to be okay with it. As far as its validity, either way will work although 99.9% of the time it's represented "0x".

[Lord_Greywolf]

me - i just open up windows calculater - set it for scientific mode, click on hex and plug in the hex nember and then hit the decimal button and covert it and place it in