|
Blake Coverett wrote:
An enumerator is the canonical example of this. This avoids poluting the public namespace.
Ummm...everywhere in the .NET Framework, enums are part of the namespace and not the class. So that's not really a canonical example...or even an example. 
When I can talk about 64 bit processors and attract girls with my computer not my car, I'll come out of the closet. Until that time...I'm like "What's the ENTER key?"
-Hockey on being a geek
|
|
|
|
|
Umm... sorry, no.
The enumerator interfaces are in the collection namespace but the actual types returned are:
ArrayList.GetEnumerator() => ArrayList.ArrayListEnumeratorSimple
ArrayList.GetEnumerator(int, int) => ArrayList.ArrayListEnumerator
Hashtable.GetEnumerator() => Hashtable.HashtableEnumerator
Hashtable.Keys.GetEnumerator() => Hashtable.HashtableEnumerator
Hashtable.Values.GetEnumerator() => Hashtable.HashtableEnumerator
... and the same for all the rest.
Hmm... as I get to the end of this I just realize you may have read it wrong. Enumerators are the canonical example. Were you thinking about Enumerations?
--
-Blake (com/bcdev/blake)
|
|
|
|
|
Blake Coverett wrote:
Enumerators are the canonical example. Were you thinking about Enumerations?
  Sorry bout that.
When I can talk about 64 bit processors and attract girls with my computer not my car, I'll come out of the closet. Until that time...I'm like "What's the ENTER key?"
-Hockey on being a geek
|
|
|
|
|
Hmmm...you can see my replies to the other two...but the most common place I've seen this is in the Windows Forms part of the framework. For instance, a ListView has several collection classes defined within it:
ListView.CheckedIndexCollection
ListView.CheckedListViewItemCollection
ListView.ColumnHeaderCollection
ListView.SelectedIndexCollection
ListView.SelectedListViewItemCollection
etc.
And that's the only place I would consider using it. Or for instance, Deklarit creates specialized DataSets with the DataRows and DataTables within the DataSet class itself:
public class MyDataSet
{
public class MyDataRow{}
public class MyDataTable{}
}
When I can talk about 64 bit processors and attract girls with my computer not my car, I'll come out of the closet. Until that time...I'm like "What's the ENTER key?"
-Hockey on being a geek
|
|
|
|
|
I'm beginning to get a clearer picture. Thanks.
|
|
|
|
|
Hey,
I have to explain my problem with an example.
I have a lot of codes to use in my application ex. sexe : man/woman; language: English/French/...
Let say sexe : man and woman are the descriptions of the code 1 and 2. These codes are in my database.
Do I make a class sexe and how?
Because in my application I have an object person and that person have a sexe.
I will program like follows :
if (person.sexe.man)
{..some code..}
and not like I am doing now
if (person.sexe = 1)
{..here some code to treath the person as a man...}
This is not very readable.
So, my question is what do I have to do with the object sexe (how will I build it) and how I use it in my person object.
thanks in advance
bene
|
|
|
|
|
If I understand what you are asking for I think you could solve it without making the sexe a custom object. Make sexe an "int" and then add this:
public class humanSex
{
public const int Male = 1;
public const int Female = 2;
}
You then would reference it to something like:
if (person.sexe == humanSex.Male)
|
|
|
|
|
Or better yet, because an enum's underlying type is an int, he could do this:
public Enum Sex
{
Male = 1,
Female = 2
}
and then check with the same thing as you have above.
When I can talk about 64 bit processors and attract girls with my computer not my car, I'll come out of the closet. Until that time...I'm like "What's the ENTER key?"
-Hockey on being a geek
|
|
|
|
|
|
 Okay okay...you win.
When I can talk about 64 bit processors and attract girls with my computer not my car, I'll come out of the closet. Until that time...I'm like "What's the ENTER key?"
-Hockey on being a geek
|
|
|
|
|
I'm designing an application in C# and I want UI a bit more exciting than the standard windows effort.(Think winamp or mediaplayer skins)
What is the best way to go about this?
Using a standard Forms.Form and and try and intercept Non client Draw commands?
Or start from the ground up inhieiting from something above form?
Help Appreciated
Conor
|
|
|
|
|
You can buy a GUI package like SharpLibrary, you can do owner-drawing yourself (alot of work), or you can wait a few months for Fluid to come out (see sig).
There are also some good skinnable controls on CP, but precious few now that Carlos Perez took his controls off. 
|
|
|
|
|
jdunlap wrote:
or you can wait a few months for Fluid to come out
Have you guys actually started any work on this yet? Or is it just a bunch of flashy HTML pages and diagrams? 
I'm just kidding, I'd just like to know where you guys are on the timeline.
When I can talk about 64 bit processors and attract girls with my computer not my car, I'll come out of the closet. Until that time...I'm like "What's the ENTER key?"
-Hockey on being a geek
|
|
|
|
|
David Stone wrote:
Have you guys actually started any work on this yet? Or is it just a bunch of flashy HTML pages and diagrams?
About 10,000* lines of code and growing. We'll release some basic controls in 1 1/2 - 2 months (probably 2).
[EDIT] * 8000 lines for C#, 2000 for C++. We are behind on C++ because of troubles w/ our dictionary and collection classes. [/EDIT]
|
|
|
|
|
jdunlap wrote:
About 10,000* lines of code and growing
Wow. 
jdunlap wrote:
We'll release some basic controls in 1 1/2 - 2 months (probably 2).
Sounds like fun. I'm looking forward to it. I looked over your diagrams a few weeks ago and they look great...very .NET-ish.
When I can talk about 64 bit processors and attract girls with my computer not my car, I'll come out of the closet. Until that time...I'm like "What's the ENTER key?"
-Hockey on being a geek
|
|
|
|
|
Let me toss in a vote for 'Just Say No'. The whole craze for skinnable applications is a bad bad thing from a user interface design/human factors perspective. It's a throwback to the days of DOS when ever application had a unique UI and everyone had to learn how to work the 'exciting' widgets and controls that application came up with.
I know it's all the rage, but please, think of the users and resist.
Just my ever humble opinion, of course....
--
-Blake (com/bcdev/blake)
|
|
|
|
|
It depends on what kind of skins you are talking about. The kind of skins that you find in Media Player and Real Jukebox sacrifice usability, whereas skins like Watercolor or other XP skins do not. A skin needs to be enough like the normal controls in that OS. That way, users can still get visual clues as to what each thing's function and state is.
|
|
|
|
|
|
Any one got any examples of drawing on NC areas of the form?
|
|
|
|
|
Hiya I am trying to use a C# dll from my MFC program. But am having a big problem.
To use the C# dll, I have changed the compiler settings in my MFC program to - Use Managed Extensions and have included #using <mscorlib.dll>.
But as soon as I change to use managed extensions, my program will not run.
I am using .Net Framework Ver 1.1 on the target machine.
Am I doing something wrong or is there another way??
Thanks.
|
|
|
|
|
Hi,
We are building a big WinForms application that references to about 30-35 assemblies (that's a lot of code, you know! :wtf
I'd like to know if there is a way to preload assemblies, when the application starts up (for example) in order to avoid delays once the application is loaded. The problem right now is that when the user opens a form for the first time, it takes a few seconds because some 3rd party controls and some other assemblies need to compile (JIT). The same window opens very quickly in subsequent calls. I'd like to have the form open quickly even on the first call.
Is there an easy way to do this?
Thanks!
Carl
|
|
|
|
|
Hmm... I'm not sure right off if there's a way to pre-load them, but you might instead try ngen'ing them when they're installed, so that thy don't have to be JIT compiled when they're loaded.
|
|
|
|
|
The problem with ngen is that it hurts the runtime performances. Preloading the assemblies would be the best solution for me since I can tolerate a delay while loading the application (a splash screen could inform the user of what's going on), but slow responsiveness is not an option for us.
Thanks!
Carl
|
|
|
|
|
Carl Mercier wrote:
The problem with ngen is that it hurts the runtime performances.
So slightly that you won't notice it, if any at all. What ngen does is just pre-compiles the executable into a native image, the same way it would be done at runtime with JIT.
|
|
|
|
|
Carl is correct - ngen'ing things does introduce an extra level of indirection to all assembly level statics. This can be a significant performance hit in some situations. There is no way to definatively state that ngen will be a win or a loss for a given application, the only thing you can do is profile it both ways yourself.
Through version 1.1 ngen's target is really for use with the framework assemblies themselves. Don't assume it's actually a win for your application. There's a good piece of this in one of the gotdotnet blogs recently but I don't have a link handy.
--
-Blake (com/bcdev/blake)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
