And are the Matchboard and Statistics features really not consuming any processor cycles when they aren't visible in the tabbed pane?
When they are hidden in an non-active tab, this may save on a graphics processor (GPU) if your computer has one, but not on the main processor (CPU).
Okay, so, doesn't it sound logical that these background processes should be frozen then? Just wondering, because of ventilator blowing this week on my MBP?
BTW: Apple's service for Apple Care in Holland isn't really overwhelming. Missing my iMac Retina now for 2 weeks already.
Crazy world. Absurdistan is everywhere.
> doesn't it sound logical that these background processes should be frozen then?
Nope. Then if you made the tab active, you would find out some old (not updated) state such as a resource not being searched or Statistics not being updated. Just close those resources that you are not using.
How can I close the MB?
You can't as it is a core function and not a resource. Though it might be a good idea to disable it to save power in the battery mode.
I second tre's proposal.
>So, for certain resources the searching in the background when the resource is hidden is useful, for others not. The latter may be all display only related resources, like Statistics and the Matchboard etc. they'll become updated as soon as they are made visible and you've navigated to the next segment.
All MT engines would qualify as 'only relevant when displayed' too. At least for me: if I need them, I make them visible, if I don't need them, they shouldn't increase my bill.