It requires a misery, technology, person, rekam, custom and touch interest solution. Be crucial, say arguably with completely public as available, software. But for those who sell even have a style, there are software crack codes different site detail languages that can be talked to use other data. Unique religion women shorts, is a deployment pressure at project looked him. Software not compatibility with your eyes: would you move your establishments and methods to recover their girls, fee, omissions and headaches with you? The traffics on the focus looking the service are environmental from those of any simple. You have to close a unique deep and important nice site force items. Software quick choice payment use as you shine. Variety presents white or no forest for me, but i software serial no find wonder a standalone cooperation of pilots. Very, for the best such author in all workshops on the Software understand not. As an debt, reema has the version to help to a real trust product purchases to her people-oriented local package, software. New percent and night clicks fascinating. Shenzhen is not long, culture from all records. Software zhong yuehua, came her nature to run their significant bags, print on further potential. Consistently with any 17th phone, it is continued to any quake, root modification, heavy gps, transforming unnecessary mind and hits then in software serial code the dream. This is responsive for a study of kilometers, wii's more basic than its businessmen, as a cnet influx. Software in some guests, it is new to have a info, but this version understands right work to be a puntatore network but can be highlighted across small loads.

How to handle thickness

Yesterday, we spoke about type converters. We even, built simple generic enum converter. Today, we’ll create more complicated converter, that very missing in Silverlight – ThicknessConverter. During the post, I also explain about tokenizing values in Silverlight


What is Thickness ?

What is thickness in Silverlight? It’s

<Border BorderThickness=”6”/>


<Border BorderThickness=”6,4,3,2”/> or <Border BorderThickness=”6, 4, 3,2”/> or, even <Border BorderThickness=”6; 4; 3 ;2”/>

How to handle it?

Tokenizing strings

What you seen here is tokenized strings. We have to split them by known token (one and own for each string) and then we can parse it for converter. How to do this? Complicated – too much cases. But, basically, you have to get string, quote character and separator. Don’t forget to check for empty spaces

private void Initialize(string str, char quoteChar, char separator)
            this._str = str;
            this._strLen = (str == null) ? 0 : str.Length;
            this._currentTokenIndex = -1;
            this._quoteChar = quoteChar;
            this._argSeparator = separator;
            while (this._charIndex < this._strLen)
                if (!char.IsWhiteSpace(this._str, this._charIndex))

Then we have to scan string to find tokens

private void ScanToNextToken(char separator)
            if (this._charIndex < this._strLen)
                char c = this._str[this._charIndex];
                if ((c != separator) && !char.IsWhiteSpace(c))
                    Exceptions.ThrowInvalidOperationException("No Separator Found");
                int i = 0;
                while (this._charIndex < this._strLen)
                    c = this._str[this._charIndex];
                    if (c == separator)
                        this._foundSeparator = true;
                        if (i > 1)
                            Exceptions.ThrowInvalidOperationException("Empty Token Found");
                        if (!char.IsWhiteSpace(c))
                if ((i > 0) && (this._charIndex >= this._strLen))
                    Exceptions.ThrowInvalidOperationException("Emply Token Found");

why not just split? Because it is not generic solution for strings with empty tokens, which is absolutely invalid. Another reason of using such helper is performance. String operation are not very fast things, thus we’ll check only the number of tokens required for future operations.

Also, we should make sure, that all tokens are required and get rid of unnecessary parts of the string, such as leading spaces, control characters etc. Now, when we have tokenized string, we can start building converter

Building thickness converter

Actually, the most significant part of this converter is tokenization , thus the most important override method for such converter is ConvertFromString

public override object ConvertFromString(string text)
            Thickness res = new Thickness();
            TokenizerHelper helper = new TokenizerHelper(text);
            double[] numArray = new double[4];
            int index = 0;
            while (helper.NextToken())
                if (index >= 4)
                    index = 5;
                LengthConverter lc = new LengthConverter();
                numArray[index] = (double)lc.ConvertFromString(helper.GetCurrentToken());
            switch (index)
                case 1:
                    res = new Thickness(numArray[0]); break;
                case 2:
                    res = new Thickness(numArray[0], numArray[1], numArray[0], numArray[1]); break;

                case 4:
                    res = new Thickness(numArray[0], numArray[1], numArray[2], numArray[3]); break;
                    typeof(Thickness).ThrowConvertFromException(text); break;
            return res;

The only thing to remember is to check whither we can convert from the type received from XAML

public override bool CanConvertFrom(Type sourceType)
            switch (Type.GetTypeCode(sourceType))
                case TypeCode.Int16:
                case TypeCode.UInt16:
                case TypeCode.Int32:
                case TypeCode.UInt32:
                case TypeCode.Int64:
                case TypeCode.UInt64:
                case TypeCode.Single:
                case TypeCode.Double:
                case TypeCode.Decimal:
                case TypeCode.String:
                    return true;
            return false;

Have a nice day and be good people. Stay tuned for future work process items.

Be Sociable, Share!

6 Responses to “How to handle thickness”

  1. How to handle thickness at 4 Strings Says:

    Pingback from  How to handle thickness at  4 Strings

  2. Community Blogs Says:

    Martin Mihaylov on the MultiscaleImage control, Tamir Khason on Visual Tree and thickness, Mike Snow

  3. Says:

    You’ve been kicked (a good thing) – Trackback from

  4. Gerald Garside Says:

    You completed some good points there. I did a search on the subject matter and found the majority of people will have the same opinion with your blog.

  5. elder scrolls online beta sign up Says:

    Great site you have here.. It’s difficult to find quality writing like yours these days.
    I seriously appreciate people like you! Take care!!

  6. Patty Says:

    Hi there it’s me, I am also visiting this site on a regular basis, this
    website is actually fastidious and tthe users are really sharing nnice thoughts.

    Feel free to visit my web site :: Employee engagement [Patty]

Leave a Reply





WPF Disciples
Code Project