Comments by kris444 - CodeProject

kris444 27-Oct-11 6:59am View

Deleted

newly created thread is simply calling ShowDialog on instance being created in UI thread, and this thread cant be involved Message loop...though this is called as UI thread?

kris444 27-Oct-11 6:57am View

Deleted

Since many of the winform applications uses Thread model as STA, thread is span in single process it is actually accessing instance that has been created in UI thread. calling ShowDialog in other thread makes that thread as UI thread?
I guess when thread is capable of handling Message Loop is called as UI thread..am i make sense?

kris444 27-Oct-11 6:54am View

Deleted

So you will end up waiting if process completes or showing up progress bar as completed before you are not finished any right?
reason is i donot have any idea how long the process takes to complete...

kris444 27-Oct-11 6:52am View

Deleted

You are mistaken, I am interested to show dialog and i dont know how long the it takes to complete the process...I cannot use this right?

kris444 2-Oct-11 22:54pm View

What exactly you are looking for?

kris444 26-Sep-11 8:48am View

what if selectedValue is object? You can simply says comboBox1.SelectedText right?

kris444 23-Sep-11 10:05am View

Hmmm...It's working when i tested...Did you checked property Categeory is returning some value?

kris444 23-Sep-11 3:56am View

DOes this mean it's working?

kris444 23-Sep-11 2:00am View

I guess you just need to specify

<%= Categeory %>

kris444 23-Sep-11 1:06am View

Hmmm....when you bind property of type string, it shouldn't give the same issue..

You added property in code-behind right?
and added

<%# Eval("Categeory")%> ?

kris444 23-Sep-11 0:43am View

oops...
ok, what i suggest is have a property like

public string Categeory
{
get
{
string catText = string.Format("{0},{1},{2}", category1, category2, category3);
return catText.Length > 45 ? catText.Substring(0, 45) : catText;
}
}
and bind
<%= Eval("Categeory")>

kris444 23-Sep-11 0:20am View

Deleted

Neither i disagree on your alternative...really appreciate for this..I only pointing to i dont want to create new collection instance to perform some action on entities :-)

kris444 23-Sep-11 0:19am View

Deleted

Yes, that's the same point i mentioned...when you call .ToList() on list ...
It actually creates new list collection and copies all objects into...

What my point is when i want to perform ForEach on collection, i dont want to create new collection instance and perform what i wanted to....

kris444 23-Sep-11 0:08am View

Deleted

Hi,
How does one clear error?
Class name says as ErrorLog...but it's not logging any..

kris444 21-Sep-11 23:42pm View

Deleted

HiBut, when you perform ToList() it actually copies to new instance of list object right?

kris444 21-Sep-11 6:31am View

Deleted

HiYou are right, it's not a good practice of calling Thread.Abort()..As far as i understand the reason for this is any exception in thread will be transfered to main thread which pops up at any point of time of application run...

But, here the case is different as i am performing only ShowDialog() and i guess its not possible to see any exception...Any Comments?

kris444 21-Sep-11 6:23am View

Deleted

HiWhen you say UI thread is it main thread you are pointing to? Is there any standards / restrictions that a child thread shouldn't start any UI form?
Probably you might be thinking / read what happens any exception in other thread? be it is UI or non UI both cases are same isn't it? Any good reason you have ? probably i am missing some...

kris444 20-Sep-11 11:57am View

This is what object state and behavior talks about...I would suggest you also consider looking
http://msdn.microsoft.com/en-us/beginner/bb308750.aspx

Comments by kris444 (Top 18 by date)