如何在使用LinkedBlockingQueue时优先考虑消费者？(How do I give priority to Consumers when using a LinkedBlockingQueue?)

 它几乎听起来像树这样的分层结构更适合显示这些数据。 但是，要回答您的问题，您希望“展平”数据的嵌套列表性质（因此，您拥有嵌套的foreach循环），而无需每次手动创建新列表。 
 
 在不了解您所拥有的任何基础设施的情况下，这里可能会有所作为，尽管有更优雅的方法可以做到这一点。 
 
 首先，添加另一个属性，该属性将表示要在ListView中显示的展平数据（有点像你在UpdateBindBaseNodList中所做的那样）。 
 
public IEnumerable<String> BaseNodeListFlattened
{
  get
  {
    foreach (var baseNode in BaseNodes)
    {
      foreach (ushort matId in baseNode.MatIDBitArrayDictionary.Keys)
      {
        yield return String.Format("{0} - {1}", baseNode.Name, matId);
      }
    }
  }
}
 
 这可以随时为您提供列表。 现在您只需要一种方法来告诉View它已经更新。 
 
 ObservableCollection很好地满足了我们的需求。 
 给定ObservableCollection<BaseNode> BaseNodes; ... 
 我们可以执行此操作（可能在ViewModel的构造函数中），以便在您更改列表时随时告诉View。 
 
this.BaseNodes.CollectionChanged += (s, e) => this.OnPropertyChanged("BaseNodeListFlattened");
 
 现在，每次向BaseNodes添加节点时，它都会触发CollectionChanged事件，然后调用OnPropertyChanged处理程序并通知View更新列表，它将读取BaseNodeListFlattened并刷新其项列表。 
 
 当然还有ListView的相应xaml ...... 
 
<ListView ItemsSource="{Binding BaseNodeListFlattened}"/>

It almost sounds like a hierarchical structure like a tree would be better suited to display this data. However, to answer your question, you want to "flatten" out the nested list nature of your data (hence the nested foreach loops you have) without manually creating a new list each time.
 
Without knowing any of the infrastructure you have in place, here is something that might work, albeit there are more elegant ways to do this.
 
First, add another property that will represent the flattened data you want to display in your ListView (kind of like you are doing in UpdateBindBaseNodList).
 
public IEnumerable<String> BaseNodeListFlattened
{
  get
  {
    foreach (var baseNode in BaseNodes)
    {
      foreach (ushort matId in baseNode.MatIDBitArrayDictionary.Keys)
      {
        yield return String.Format("{0} - {1}", baseNode.Name, matId);
      }
    }
  }
}
 
This gets you the list anytime you ask for it. Now you just need a way to tell the View that it has been updated.
 
An ObservableCollection does nicely for our needs.
 Given ObservableCollection<BaseNode> BaseNodes; ...
 We can do this (perhaps in the constructor of your ViewModel) to tell the View anytime you change the list. 
 
this.BaseNodes.CollectionChanged += (s, e) => this.OnPropertyChanged("BaseNodeListFlattened");
 
Now every time you add a node to your BaseNodes it will trigger the CollectionChanged event which will then call the OnPropertyChanged handler and inform the View to update the list, where it will read BaseNodeListFlattened and refresh its list of items. 
 
And of course the corresponding xaml for the ListView... 
 
<ListView ItemsSource="{Binding BaseNodeListFlattened}"/>