• Fixed max port bug. Previously, the max port was set to 52000, but now covers up to 65535.
• Added the ability to select the input microphone.

It’s important to note that the software uses the default microphone input when the application starts, if you wish to use a different input, then change the microphone input in the Configuration tab.

Over the next few days, expect more updates to be released. There needs to be some more changes made to the way the input microphone selection works, and also possibly support for WMA files.

WPF Value Converters

To change monotone cell values to something more visual stimulating, we’ll make use of two value converter interfaces that can be found in the .NET framework called IValueConverter and IMultiValueConverter. As the names suggest IValueConverter converts a single value and IMultiValueConverter can convert an array of values based on custom logic.

To start we’ll create a class that inherits the IMultiValueConverter interface with the Convert and ConvertBack methods generated from the inheritance.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
namespace xamDataGrid_ConditionalFormatting.ConditionalConverters

{

    class TotalSalesColorConverter: IMultiValueConverter

    {

        #region IMultiValueConverter Members



        public object Convert(object[] values, Type targetType, object parameter, System.Globalization.CultureInfo culture)

        {

            if (values != null)

            {

                if (values[0] != DependencyProperty.UnsetValue && values[1] != DependencyProperty.UnsetValue)

                {

                    //Insert your custom logic here and return a SolidColorBrush

                }

            }

            return Binding.DoNothing;

        }



        public object[] ConvertBack(object value, Type[] targetTypes, object parameter, System.Globalization.CultureInfo culture)

        {

            throw new NotImplementedException();

        }



        #endregion

    }

}

In the sample project included with this article, custom logic was used to compare the estimated sales versus the total sales, which then returns a green SolidColorBrush for sales above estimate, and a red SolidColorBrush for sales below estimate. The Convert method below shows our custom logic.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
        public object Convert(object[] values, Type targetType, object parameter, System.Globalization.CultureInfo culture)

        {

            if (values != null)

            {

                if (values[0] != DependencyProperty.UnsetValue && values[1] != DependencyProperty.UnsetValue)

                {

                    Decimal EstimatedSales = (Decimal)values[0];

                    Decimal TotalSales = (Decimal)values[1];



                    if (EstimatedSales > TotalSales)

                        return new SolidColorBrush(Colors.Red);

                    else

                        return new SolidColorBrush(Colors.Green);

                }

            }

            return Binding.DoNothing;

        }

Next, we’ll create the class to inherit from IValueConverter and take a look at the skeleton. You’ll notice that the structure of the Convert method is nearly identical to IMultiValueConverter.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
namespace xamDataGrid_ConditionalFormatting.ConditionalConverters

{

    class YearColorConverter: IValueConverter

    {

        #region IValueConverter Members



        public object Convert(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture)

        {

            if (value == null)

                return Binding.DoNothing;



            //Insert your custom logic here and return a Color

            //Typically in this custom logic you'll use a switch/case or if statement to

            //   process the correct data type.



            return Binding.DoNothing;

        }



        public object ConvertBack(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture)

        {

            throw new NotImplementedException();

        }



        #endregion

    }

}

For the sample project we used the Year column to check for a specific year value and returned a Color to set the background of the cell.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
        public object Convert(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture)

        {

            if (value == null)

                return Binding.DoNothing;



            if (value is String)

            {

                String Year = (String)value;

                switch (Year)

                {

                    case "2010":

                        return Colors.LightBlue;

                    case "2011":

                        return Colors.LightGray;

                    default:

                        return Colors.White;

                }

            }

            return Binding.DoNothing;

        }

XAML Integration

Now that we have the two necessary classes created for our conversion to a conditionally formatted cell, we’ll have to add the namespace to the class at the top of our XAML source.

1
xmlns:cc="clr-namespace:xamDataGrid_ConditionalFormatting.ConditionalConverters"

With the namespace now in place we can add references to each converter inside the Windows.Resources tags. This gives us the ability to use the converters as a static resource in the parts of XAML where we need it as you’ll see coming up.

1
2
3
4
    <Window.Resources>

        <cc:TotalSalesColorConverter x:Key="totalSalesColorConverter" />

        <cc:YearColorConverter x:Key="yearColorConverter" />

    </Window.Resources>

To make use of the converters we need to create the Style/Setter tag groups inside the XamDataGrid.Resources tags to target the CellValuePresenter class. From that point you can reference the necessary property in the Setter tag. In this article we’re using Foreground property for the total sales conversion against the estimated sales, and Background property for the year column.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
            <igDP:XamDataGrid.Resources>

                <Style TargetType="{x:Type igDP:CellValuePresenter}" x:Key="TotalSalesFieldStyle">

                    <Setter Property="Foreground">

                        <Setter.Value>

                            <MultiBinding Converter="{StaticResource totalSalesColorConverter}">

                                <Binding Path="DataItem.SalesEstimate" />

                                <Binding Path="DataItem.TotalSales" />

                            </MultiBinding>

                        </Setter.Value>

                    </Setter>

                </Style>

                <Style TargetType="{x:Type igDP:CellValuePresenter}" x:Key="YearFieldStyle">

                    <Setter Property="Background">

                        <Setter.Value>

                            <SolidColorBrush Color="{Binding Path=DataItem.Year, Converter={StaticResource yearColorConverter}}" />

                        </Setter.Value>

                    </Setter>

                </Style>

            </igDP:XamDataGrid.Resources>

The final step in wiring up the conditional formatting happens inside the Field.Settings tags. By setting the CellValuePresenterStyle as the static resource key we created in XamDataGrid.Resources our custom styling will process the converter binding and give our grid some eye catching color.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
            <igDP:XamDataGrid.FieldLayoutSettings>

                <igDP:FieldLayoutSettings AutoGenerateFields="False" />

            </igDP:XamDataGrid.FieldLayoutSettings>

            <igDP:XamDataGrid.FieldLayouts>

                <igDP:FieldLayout>

                    <igDP:Field Name="Salesman" />

                    <igDP:Field Name="Year">

                        <igDP:Field.Settings>

                            <igDP:FieldSettings CellValuePresenterStyle="{StaticResource YearFieldStyle}"/>

                        </igDP:Field.Settings>

                    </igDP:Field>

                    <igDP:Field Name="SalesEstimate" Label="Estimated Sales" />

                    <igDP:Field Name="TotalSales" Label="Total Sales">

                        <igDP:Field.Settings>

                            <igDP:FieldSettings CellValuePresenterStyle="{StaticResource TotalSalesFieldStyle}"/>

                        </igDP:Field.Settings>

                    </igDP:Field>

                </igDP:FieldLayout>

            </igDP:XamDataGrid.FieldLayouts>

Conclusion

That’s all there is to it! Now that you see how to conditionally format cells of the XamDataGrid you can easily begin to expand on this concept if you need further formatting by making use of the other properties that can be found inside the CellValuePresenter class along with the Setter tags.

For example the Ingenious Streaming Media DJ V1 software uses a mixer that holds 2 channels of audio. One for the audio track, and one for the microphone (if one exists). Now if we toss into the mix a DJ that mixes music, adding in another audio track channel we can start to fade between the two audio tracks to create mixing. Basically the same thing you see in the software Virtual DJ.

I’m also experimenting with an idea that should amount to “scratching” an audio track when I’m done. We’ll see how that goes, sometimes the result of shots in the dark can be successful or have really funny results.

This software took a lot of work to get it to this point and there’s a lot more planned for it, and other future software releases that are much more advanced for the hardcore DJs out there.

Over the next 3-6 days I’ll be in the transition period of changing web hosts for the business site I run ( igsweb.net ). It handles various business software applications I’ve developed and also the business related email I receive. I’ll be trying to minimize downtime of the email and support portal as best I can by getting the DNS updated as soon as possible, but as the engineers will always say, it can take up to 3 days to update the DNS across the web.

This website and software attached to it will not be affected by the change. Please be patient if attempt to contact me by email, as it may get bounced back if an email is  sent during the downtime of the transition.

This week in addition to the marketing campaign for Ingenious Streaming Media DJ, I need to work on an affiliate program for it in one special market. I noticed that some places charge for joining their affiliate, but frankly I don’t understand that. If someone is bringing you sales and leads why charge a setup or joining fee?

We’ll have to see how my first marketing campaign goes, but I’m feeling pretty good about everything. Wish me luck!

Objectives
I. Easy to Use Payment System for Staff and Tenants.
With the failure of their old payment Surreal Estates needed a ground up solution that could integrate tenant data and process their payments again as soon as possible. A unique permission based object was also necessary to manage the land parcel by management and for tenants to use on their own.

II. Track Payment History and Land Transactions
Previous tracking of payment history and land transactions lacked several important integrity checks. They needed a tracking solution to streamline analysis and make management of the land parcels and their financials an easy task.

III. Website for Staff and Management Operations
With no earlier method for collaboration or solid reporting solution, Surreal was looking for a way to compile their business data into useful dashboard style information and input screens for admins to handle day to day operations.

Solution
I. Versatile Tier Payment Utilising LSL
Using Linden Labs’ LSL scripting language a multiple state payment object was developed that interacted with admins and tenants based on group permissions.

II. Dedicated SQL Server Backend
A new database schema was developed and included the importing of previous system data to seamlessly continue where their operation left off. This backend not only integrated with the LSL scripting in-world, but also tied the web interface in with realtime information. Each payment or management transaction was logged with additional information to maintain the best level of data integrity.

III. Web Interface Management Dashboard
A powerful web interface was created that used a user and group based permissions system. It allowed for various staff to handle the roles they were assigned without giving them too much administrative access. By using the realtime information gathered by the SQL Server, Surreal management had easy access to reports and dashboard style information about daily, monthly, and yearly business data.

One of the most important things I went for when designing this software was to make it super user friendly so that anyone can use it. If you’re familiar with a program called Sam Broadcaster or any of the similar programs out there, you’d remember how confusing that was the first time you loaded it up. This program has similar functionality and is a million times easier to use and less bloated, not mention it’s going to have a nice price tag when I’m done that won’t hurt your bank account.

I can’t wait to get this out there in the world and give out a few free licenses to testers and get some feedback. Stay tuned for more information!

Objectives

I. Expand Information Capture Capabilities
Operating on a limited legacy software system, they needed a custom solution with a versatile & flexible database backend that would allow them to link the various pieces of collected information together.

II. Modernize Internal Processes
Most of the business was ran using paper data collection, with a minimal data entry system to hold the information. Pamela Rose & staff wanted to stream line this work process and digitalize their records for a more accessible and searchable format.

III. Improve Auction Agent Mobility & Communication
The auction agents operated through company/personal email while on the road for their auction information. They needed a better way to become mobile and keep the office records at their fingertips no matter where they might be.

Solution

I. Expanded Database
We converted their legacy database system to Microsoft SQL Server, optimized the columns and table structures, and created relationships between the data to tie all their auction processes together.

II. Process Management
Meeting with the client and discussing the work flow we created a process in the software to cut hours off their usual work and digitalize everything in the process.

III. Smart Client Technology
With the auction agents working out of the office almost all of the time we took advantage of Smart Client technology. This technology makes it possible to take your work with you no matter where you are as long as you have an internet connection. Combing this with ClickOnce we developed a completely mobile product that was also automatically updatable when new versions get released.

The Township of Monclova is a beautiful area of Ohio that lies partly upon the Maumee River at the head of the Rapids, and is included in the oldest settled sections of the Maumee Valley.

Objectives

I. Extend Township Fuel Pumps
Working with a fuel pump system hardware that has limited data capabilities develop an information system to capture and store the gas pump transactions.

II. Reporting
Using data stored from the fuel transactions create detailed reports that can be used by the township and other local governments for fuel accounting.

Solution

I. Database Backend
Taking advantage of a Microsoft SQL Server backend, we provided the fuel system with an integration to dump its transactions. Using a SQL Server provides the township with more functionality that’s scalable and flexible for all their management needs.

II. Integrated Reporting
With the client needing very few reports the reporting solution was directly integrated into the software for fast, easy, and on the spot reporting.