Windows Actions

[mordero]

its pulling different information about each drive you have in your computer...

[Jeff]

Originally Posted by Storm33229

tbchwy, I don't fully understand this. Can you explain a bit more about what that does?

It just gets info about each Hard drive on the computer nothing more nothing less, but you can use this info for things like grabbing handles on the harddrive to read the raw sectors and such

[Storm33229]

Originally Posted by Jeff

It just gets info about each Hard drive on the computer nothing more nothing less, but you can use this info for things like grabbing handles on the harddrive to read the raw sectors and such

do you have to use both blocks of code? or just one or the other?

[Jeff]

Originally Posted by Storm33229

do you have to use both blocks of code? or just one or the other?

depends on what your doing, the 1st is kinda like a hashtable, and second is aquiring its values by using its keys :/

[Storm33229]

Originally Posted by Jeff

depends on what your doing, the 1st is kinda like a hashtable, and second is aquiring its values by using its keys :/

so...confusing...*dies*

[Jeff]

Originally Posted by Storm33229

so...confusing...*dies*

about what?

[Storm33229]

Originally Posted by Jeff

about what?

Uhh. Hashtables? =/

[mordero]

HashTable Tutorial in C# (C#.NET)
Working with HashTable in C# 2.0
Hashtable class at C# Online.NET (CSharp-Online.NET)

http://www.google.com/search?sourceid=navclient&ie=UTF-8&rlz=1T4GGIH_enUS208US208&q=c%23+hashtable

[Jeff]

Originally Posted by Storm33229

Uhh. Hashtables? =/

Dictionary<key, value> ? that better for you? same concept, but not type-casted.

[Storm33229]

Originally Posted by Jeff

Dictionary<key, value> ? that better for you? same concept, but not type-casted.

What's casted mean? Grr.. my programming books don't tell me these things. =/

[Jeff]

Originally Posted by Storm33229

What's casted mean? Grr.. my programming books don't tell me these things. =/

lets say you have(for this example im gonna use runuo code cause i tihnk u will understand that better)

public void Method( Mobile m )
{
   if( m is PlayerMobile )//Check if m is of type PlayerMobile
   {
       PlayerMobile pm = (PlayerMobile)m;//Cast m as a PlayerMobile
       pm.MethodTwo();
   }
}

In that example I Casted Mobile m as a PlayerMobile.

Hashtable works the same as an arraylist in the sense that whenn you pull an object out of it, its only an object and needs to be cast as its real valuetype. Dictionary<type, type> solved this issue the same way List<type> solved it for an ArrayList.

[mordero]

As a side note: when you put anything into a hashtable, its "boxes" it into an object (since everything is derived from an object). So you must "unbox" everything that comes out of a hashtable and cast it to its correct type. However, this could throw an exception if you cast it wrong, so a dictionary solves this problem because you no longer have to cast whatever you take out of it.

[noobie]

boxing/unboxing is only true for value types.

and casting wrong was not the problem, it was efficiency. casting objects is a very high overhead.