Wednesday, February 2, 2011

Can You Order A Replacement Remote For An Ihome?

Some people want to die ... literally ...

I love skiing and almost anything that means: moving fast, in the snow, in water, or on something that has wheels. I can´t imagine any sport that meets those requirements and I don´t like. Don´t practice them all of course, but love them.

But there´s some people out there that seems to be always chasing death. I honestly don´t understand how can anybody jump from 80 meters high (like a 30 floor building), hoping that the snow below will be soft, and deep enough…

I really don´t get it. What are the chances of surviving that?

Other insane skiing videos ( in HD ):

 

Simply amazing…

What Does A Low Lymphocyte Count Mean

OTURIA (1921 m.)

Huesca minus 5 degrees at 8 am. Monrepós least 4. Sabiñánigo least 12. We thought we had hit bottom with the thermometer, but no. In Javierre the Bishop (872 m), place of departure, the thermometer surprises us less nde 13.5 degrees. A phenomenal day to stay in bed. The route we will do today, which will coincide with the vertical kilometer Oturia. We have before us a little over 1000 m. of positive slope and 6 km away. Our friend Samuel decides to climb also the same place, but running. A cost him 59 minutes to reach the top. To us 2 hours.
This is the description indicating the BLOG Samuel the Vertical Kilometer:
Javierre Since the first 150m are to pick up asphalt and the ascent to the summit. A piece of mountain road to stretch through where other predominantly Salagon 150m away, where if the ground is wet, the shoes we can charge a little mud. From here the climb becomes a clear path dominated rock songs and loose rock, which does not prevent it running at pace. To Sta Orosia the trail ascends between zigzags and pine forest. At the top of the grass for about 200m the road slope and looking lost in thickets and Bojes way to attack and steep peak Oturia about 350m with 1921m of vertical height between loose rock and mountain meadow , where part of the climb has an angle of approximately 20%. Despite the punishment which was subject on the thermometer, the morning was fantastic to ride around the bush .
Dry weather, glorious sunshine and 2 degrees below zero at the top.
The descent to perform circular Satue. Path coincides with a decrease of Puyada to Oturia. Beautiful path that leads through pines, sometimes crossing the ravine of the gorges, to Satue, where we get one of the jewels of Romanesque Serrablo S. Church Pedro de Lárrede (s. X). Few
Satué meters after leaving a clear path to the right, we will bring in a few minutes Javierre. PHOTOS

.

Tuesday, February 1, 2011

Pinnalcle Tv Pro 64bit

Enabling / Disabling properties in the PropertyGrid at runtime

Many people knows about the benefits of using PropertyGrids in user interfaces.

You probably know about the System.ComponentModel namespace, and how it can help you customizing the behavior of classes and their properties when edited through controls like the PropertyGrid. One of the attributes you can find in that namespace is the ReadOnly, which will make a property to be read only and appear in gray (even if it has the Set accessor).

The problem with this attribute is that it must be defined at build-time. Sometimes, it is very useful (and improves the User Experience quite a bit), to enable or disable properties at runtime.

Imagine the following example, where we have a “UserData” class:

public class UserData

{

...

 

        public string Country

        {

            get { return mCountry; }

            set { mCountry = value ; }

        }

        public string State

        {

            get { return mState; }

            set { mState = value ; }

        }

}

Now, imagine you want the user to fill the “State” field only in the case he selected U.S. as his Country. In such a case, you need to make this change at Runtime.

There are several solutions for this, but I find the following one to be the most elegant, as it´s coded in the “UserData” class itself. The final code looks like:

[ RefreshProperties (System.ComponentModel. RefreshProperties .All)]

[ ReadOnly ( false )]

public string Country

{

  get { return mCountry; }

  set

      {

      mCountry = value ;

      PropertyDescriptor descriptor = TypeDescriptor .GetProperties( this .GetType())[ "State" ];

      ReadOnlyAttribute attribute = ( ReadOnlyAttribute )

                                    descriptor.Attributes[ typeof ( ReadOnlyAttribute )];

FieldInfo fieldToChange attribute.GetType = (). GetField ( "IsReadOnly" ,

, & # 160; ; System.Reflection. BindingFlags . Nonpublic

.Instance);                   fieldToChange.SetValue(attribute, mCountry !=

"U.S." );       }

}

[

ReadOnly

(

true )] public

string State {

  

get

{

return mState; }    set

{ mState =

value ; } }

Some Tips

1.- We obviously change the “ReadOnly” attribute of the “State” property in the setter accessor of the property “Country”. That´s the exact point where we know if State should be enabled or disabled.

2.- It is important to add the “RefreshProperties” attribute to the “Country” property. That will force the PropertyGrid control to refresh all it’s properties every time the value of “Country” changes, reflecting the changes we made to the attributes of “State”

3.- In order to work properly all of this, it is important to statically define the “ReadOnly” attribute of every property of the class, to whatever value you want. If not, changing the attribute at runtime that way, will wrongly modify the attributes of every property of the class.

Hope it helps!

More Info

At The Code Project

At C-Sharp Corner

Cheers!