|
Well my problem is the next buddies
I have a GridView, well Actually a RagGrid From telerik control
I get the data executing a StoreProcedure and storing in a Datatable
the I just use the next code
<br />
DataTable dtListValues = null;
dtListValues = LoValues.oListValues(Values.PKValue);
this.rgValues.DataSource = dtListValues;
this.rgValues.DataBind();
and then the page ends with this
NameColumns PKValue NameValue isActive
but!! I don't want to use this names!! 
And to "fix" this I try to use this
<br />
dtListValues.Columns[0].Caption = "Code";<br />
dtListValues.Columns[1].Caption = "Name";<br />
dtListValues.Columns[2].Caption = "Active";<br />
I already used this code after and before executing the DataBind
But!!!! It doesn't work!!! =(
Could someone Tell Me where I'm wrong  ?
I hope you can help me please
thanks in advanced
Greetings!!!
|
|
|
|
|
I'm not familiar with that datagridview but I would look to it's properties for setting the caption (column header) instead.
|
|
|
|
|
Hello!!
Yes, I try this too, and I concluded that the correct code (according to my nerves [¬_¬])
was this :
<br />
dtListValues.Columns[0].Caption = "Code";<br />
dtListValues.Columns[1].Caption = "Name";<br />
dtListValues.Columns[2].Caption = "Active";<br />
because when I was looking the properties in debugging time I saw the names of the captions in this properties
but when I try to change it, It doesn't work
In any way, too much thanks for your Help!!
|
|
|
|
|
Okay, so me and my buddy were having this discussion today.
Assume a case in C# where we have two classes, class A and class B, with A having an array of objects of B.
Now when we want to use these classes from a different class C (without inheritance that is), we create two instances of A and B. However all members of class A and a few from B are to be initialized before they can be used in C.
So the argument was abouthow to have this initializing logic in the constructor for class A. But then that would mean having a part of the logic also in the constructor for class B.
Instead why not having a public method in class A which takes care of this logic?
The argument stopped at how much of memory duz it take to invoke and execute two constructors instead of one public method?
Any takers?
------------------------------------
Vision is the ability to see the invisible
|
|
|
|
|
The constructor for B should construct a B.
The constructor for A should construct an A, which may involve instantiating the array of B, and may involve instantiating a number of Bs to put into that array.
The constructor for C should construct a C, whatever that entails.
Or... each class should have an Initialize method that does what the constructor would do otherwise.
Perhaps you didn't ask the question well.
|
|
|
|
|
Or you could use the Factory Pattern
Scott P
"Run for your life from any man who tells you that money is evil. That sentence is the leper's bell of an approaching looter." --Ayn Rand
|
|
|
|
|
Yes, but there still need to be constructors and maybe initializers.
|
|
|
|
|
Well the question is, is it better to have two different constructors (A & B) to execute when we can one public method (in A) to do this job for A & B constructors?
The main purpose is to save the CLR overhead of executing two different constructors than one public method.
Duz it make sense now?
------------------------------------
Vision is the ability to see the invisible
|
|
|
|
|
Have you timed it yourself? You could also put together a test app and run it through ildasm to look at the IL. Regardless, the constructors get called if they're in a public method or not. The constructor in B (there's one that the compiler generates even if you don't type it in yourself - use ildasm and see), it gets called. Period. Any instance of any object needs a sync block index and a type pointer, plus all the space for it's members on the heap. Doesn't matter if you make your object family in a Factory Method or not, they get called. With the Method call there's additional overhead for putting the instruction on the stack and making the call, plus the return.
Scott P
"Run for your life from any man who tells you that money is evil. That sentence is the leper's bell of an approaching looter." --Ayn Rand
|
|
|
|
|
Thanks a lot Scott,
carbon_golem wrote: Have you timed it yourself?
Nope I havent timed it yet, how do i do that?
I did look at the ildasm. Thanks a lot, it cleared a big stumble in the thought process.
Okay agreed that with a method call, there is an additional overhead for puting the instruction on the stack and the return.
However compare it to the scenario where the class A and class B objects are being created more than once in Class C, would it be more economical to invoke the constructors everytime and initialize the members, even if we dont need them to be initialized; or just call a method once and pass the object references to initialize them once?
The IL clearly showed how a simple initialization like string.Empty is costly to refer to the Empty member of the system.string. Why do it twice? why not do it just once in a method call and avoid the redundancy?
Agreed there is a cost to make the call to the constructor and the method, but what about the cost of redundancy by calling the class ctor but not using that object any further.
Pass the object to a method that initializes/constructs it when it is needed.
What say?
------------------------------------
Vision is the ability to see the invisible
|
|
|
|
|
Spykraft wrote: carbon_golem wrote:
Have you timed it yourself?
Nope I havent timed it yet, how do i do that?
Look at the Stopwatch class, create a bunch of instances in a tight loop and time it. divide by your for loop parameter.
Spykraft wrote: However compare it to the scenario where the class A and class B objects are being created more than once in Class C, would it be more economical to invoke the constructors everytime and initialize the members, even if we dont need them to be initialized; or just call a method once and pass the object references to initialize them once?
That depends... if you're using the class as purely an initializer and not a member, then yes it is more economical. Say you're using class A to initialize class B then throwing A aside, then that's better to use it that way. And that's leaning more toward the Factory Pattern.[^].
If you're keeping A as a member in C then in that situation, then you'll probably want to give C it's own copy. If you make A temp = new A(); and pass temp to every instance of C that is being created, then all C's copies of A point to the same object. Thus any changes to A have a profound effect on your program. If that's the situation, then consider a redesign. But for the sake of argument, that's the fastest solution because there's one initialization and method calls proportional to the number of C's you have.
Hope this helps...
Scott P
"Run for your life from any man who tells you that money is evil. That sentence is the leper's bell of an approaching looter." --Ayn Rand
|
|
|
|
|
Spykraft wrote: Duz it make sense now?
No, even less so.
|
|
|
|
|
I have a form with a datagridview and the following class to handle the data keypress.
What code is missing to use the class.
I do not want to put this as a control.
I am new at this so anyhelp would be appreciated.
namespace WindowsApplication1
{
public partial class Form1 : Form
{
public Form1()
{
InitializeComponent();
}
private void Form1_Load(object sender, EventArgs e)
{
}
private void dataGridView1_EditingControlShowing(object sender, DataGridViewEditingControlShowingEventArgs e)
{
DataGridViewTextBoxEditingControl dText = (DataGridViewTextBoxEditingControl)e.Control;
dText.KeyPress += new KeyPressEventHandler(/////);
}
}//end form class
//********************************************************************
#region DataGridViewControlClass
public class DataGridViewEnter : DataGridView
{
protected override bool ProcessDialogKey(Keys keyData)
{
Keys key = (keyData & Keys.KeyCode);
if (key == Keys.Enter)
{
return this.ProcessRightKey(keyData);
}
return base.ProcessDialogKey(keyData);
}
public new bool ProcessRightKey(Keys keyData)
{
int DGVfirstcolumn = 0;//First column shown
int DGVlastcolum = 5;//Last Column shown
Keys key = (keyData & Keys.KeyCode);
if (key == Keys.Enter)
{
//works on the current line
if ((base.CurrentCell.ColumnIndex == (DGVlastcolum)) && (base.CurrentCell.RowIndex == (base.RowCount - 1)))
{
try
{
((BindingSource)base.DataSource).EndEdit();
((BindingSource)base.DataSource).AddNew();
}
catch
{ } // do nothing
base.CurrentCell = base.Rows[base.RowCount - 1].Cells[DGVfirstcolumn];
return true;
}
//add a new line
if ((base.CurrentCell.ColumnIndex == (DGVlastcolum)) && (base.CurrentCell.RowIndex != base.NewRowIndex))
{
base.CurrentCell = base.Rows[base.CurrentCell.RowIndex + 1].Cells[DGVfirstcolumn];
return true;
}
return base.ProcessRightKey(keyData);
}
return base.ProcessRightKey(keyData);
}
protected override bool ProcessDataGridViewKey(KeyEventArgs e)
{
if (e.KeyCode == Keys.Enter)
{
return this.ProcessRightKey(e.KeyData);
}
return base.ProcessDataGridViewKey(e);
}
}
#endregion
}//end namespace
|
|
|
|
|
|
hi
i want to generate typed dataset, for this work, i need an article to explaining how to create typed dataset ?
thanks
|
|
|
|
|
Hello everyone,
I am learning from "Garbage Collector Basics and Performance Hints",
http://msdn2.microsoft.com/en-us/library/ms973837.aspx
Two questions,
1. In the pattern "Too Many Pointers", what means "they merely "slide" together to remove the wasted space"?
2. In the pattern "Too Many Object Writes", I do not quite understand the emunerator and collector pattern, could anyone provide some brief pseudo code please?
--------------------
If you are, for instance, doing simple operations in some kind of enumerator class, you might find that you need to move some of your key pointers from the main collection into the enumerator at every step. This is actually something you might want to avoid, because you effectively double the cost of copying those pointers around due to the write barrier and you might have to do it one or more times per loop on the enumerator.
--------------------
thanks in advance,
George
|
|
|
|
|
George_George wrote: what means "they merely "slide" together to remove the wasted space"?
Defragment
|
|
|
|
|
Thanks Colin,
How about your points of my question item 2? 
regards,
George
|
|
|
|
|
George_George wrote: could anyone provide some brief pseudo code please?
The "for instance" is just talking about copying a reference from the collection into an enumerator of the collection as a method of implementing an enumerator. Anytime you copy a reference the GC system has to track it so it comes at an expense. There isn't much you can do in a GC environment that doesn't come at an expense.
These two reasons are of course complemented by the usual reasons for not doing too many writes in any kind of program. All things being equal, it's better to touch less of your memory (read or write, in fact)
led mike
|
|
|
|
|
Thanks led,
Two more comments,
1.
If this practice is bad, because of two many writes, what is the preferred implementation? Could you describe please (without using enumerator)?
2.
I have a stupid question, what means enumerator in C#? Which API? Could you show me some samples please?
(I understand container or collect like List<>, but I am confused about what means enumerator?)
regards,
George
|
|
|
|
|
|
Thanks led mike,
1.
Does the article mean using foreach is better or not according efficiency and effectiveness of GC?
2.
Any pros and cons compared with using foreach and using simple index to loop, like
for (int i = 0; i < count; i++)
{
}
regards,
George
|
|
|
|
|
|
Thanks led mike,
I like both links and I take some time to read through. I do not quite understand this sentence in the 1st link,
"It remains true that only 10% of the code needs optimization, and that algorithmic efficiency is often the driving factor."
What means "algorithmic efficiency" and "driving factor"?
regards,
George
|
|
|
|
|
George_George wrote: What means "algorithmic efficiency"
George, why to you keep asking us question for which there is already a perfectly acceptable and easily found[^] answer?
George_George wrote: What means .... "driving factor"?
That means every project has it's own factors related to optimization needs. They can be very different from project to project. For example the use model of a system typically provides an understanding of many of these factors.
led mike
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
