This is great tool, but unfortunately on our bigger project is nearly unusable.
We have 1700 resource keys in approximately 100 resource files.
When I open ResxManager, visual studio hang to nearly 10 seconds.
Next action unselect all resources, hang next 10 seconds. Practicaly every change selection do this hang.
When I try scroll resources and some name are too long. The ResXManager change layout to show full name, but hang another 5 seconds before change layout.
I profile this preformance issue and attach results .
Results was measured during this sequention actions:
- unselect ALL resources
- select ALL resources
- Scroll from start to end resources
- Scroll from start to end resources
In attachments are unrolled two biggest method.
Thanks .
Comments: ** Comment from web user: tomenglert **
"ProcessMessages": If you remove that call, you will profile only half of the code involved, because then the layout will be done afterwards - that's why it looks faster.
"CollectionChanged events": There is nothing much to optimize, because the ObservableCollection class does not have AddRange or RemoveRange methods, so it will always fire single events. The code in the wrapped collection is just for sake of completeness, but in real life it will never be called with more than one item.
The real bottleneck was that the CollectionView used for grouping was always active, even in the flat view. Now it's created on demand only, this made it about 5 times faster.
Maybe you can get the latest sources and give me some feedback how much this is on your machine.