Click here to Skip to main content
11,704,768 members (50,106 online)

Comments by George Tryfonas (Top 5 by date)

George Tryfonas at 27-Jul-11 4:51am View
Reason for my vote of 5
This is a very clear presentation of a well known problem and one of its possible solutions.
George Tryfonas at 11-Mar-11 8:33am View
Reason for my vote of 3
It's a good attempt, nevertheless this method is quite restricted given that you must know the columns for which you pivot in advance. It does not cover the general case where, in your particular example, stores may be added or removed.
George Tryfonas at 4-Mar-11 11:44am View
It may be a stupid thing to ask, but did you rename the element when you changed the control from ListBox to ElementFlow? If you did, did you make sure to update your binding?
George Tryfonas at 23-Feb-11 13:51pm View

thanks for your complete and excellent answer. I'll find my way from here.

George Tryfonas at 23-Feb-11 8:29am View
John, thanks, these are good suggestions. However, there is one key fact that I forgot to mention: this array may contain tens of thousands up to millions of elements. However, few of them change at a time. Unfortunately, if I create a worker thread that moves items from the array to an observable collection, it will take quite some time until it's done moving them -- which means that refreshing the UI will be quite slow.

On the other hand, you suggest that I create a thread that "watches" the array. By that I understand that you mean that the thread can determine which elements of the array have changed. Could you please elaborate a bit more? If I could do that then I could wrap the array around a custom collection class and send the approriate collection change notifications (i.e. the Replace action).

If there are no better suggestions than the ones you have given I will have to accept your answer as the best one. Thanks for the effort anyway.

Advertise | Privacy | Mobile
Web04 | 2.8.150819.1 | Last Updated 1 Jan 1900
Copyright © CodeProject, 1999-2015
All Rights Reserved. Terms of Service
Layout: fixed | fluid