# \#deprecation

**URL:** https://discourse.paraview.org/tag/deprecation/13.md

[Latest](https://discourse.paraview.org/latest.md) · [Categories](https://discourse.paraview.org/categories.md) · [Tags](https://discourse.paraview.org/tags.md)

---

## [How can I map distances between joint areas in contact using ParaView 5.9.0 ?](https://discourse.paraview.org/t/how-can-i-map-distances-between-joint-areas-in-contact-using-paraview-5-9-0/6559)

<div class="topic-metadata">

**Author:** [@Pppp](https://discourse.paraview.org/u/Pppp)\
**Replies:** 2\
**Last updated:** [February 26, 2021, 1:52pm UTC](https://discourse.paraview.org/t/how-can-i-map-distances-between-joint-areas-in-contact-using-paraview-5-9-0/6559 "2021-02-26T13:52:33Z")

</div>

How can I map distances between joint areas in contact using ParaView 5.9.0 ?

---

## [Deprecating multi-client support](https://discourse.paraview.org/t/deprecating-multi-client-support/1439)

<div class="topic-metadata">

**Author:** [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)\
**Replies:** 12\
**Last updated:** [July 3, 2020, 12:48pm UTC](https://discourse.paraview.org/t/deprecating-multi-client-support/1439 "2020-07-03T12:48:33Z")

</div>

ParaView has long supported a rarely used feature, multi-clients – where multiple paraview clients can connect to the same pvserver. While it’s a really neat feature, it’s tedious to maintain and support robustly. I want…

---

## [Catalyst Edition status in 5.7 and 5.8](https://discourse.paraview.org/t/catalyst-edition-status-in-5-7-and-5-8/1510)

<div class="topic-metadata">

**Author:** [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)\
**Replies:** 13\
**Last updated:** [January 21, 2020, 10:39pm UTC](https://discourse.paraview.org/t/catalyst-edition-status-in-5-7-and-5-8/1510 "2020-01-21T22:39:25Z")

</div>

Hi all, With the new build system having landed, we’ve discussed internally what is to happen with the Catalyst Editions. The catalyze.py has not been updated for the new CMake code and after discussion of what should h…

---

## [remove legacy catalyst export wizard](https://discourse.paraview.org/t/remove-legacy-catalyst-export-wizard/1440)

<div class="topic-metadata">

**Author:** [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)\
**Replies:** 3\
**Last updated:** [March 12, 2019, 12:46am UTC](https://discourse.paraview.org/t/remove-legacy-catalyst-export-wizard/1440 "2019-03-12T00:46:53Z")

</div>

What’s our plan for removing the legacy Catalyst export wizard? I’m referring to the Generate Script -deprecated and Data Extract Writers -deprecated menu options. cc: @Dave\_DeMarle

---

## [Dropping support for OS X 10.11 (El Capitan)](https://discourse.paraview.org/t/dropping-support-for-os-x-10-11-el-capitan/1431)

<div class="topic-metadata">

**Author:** [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)\
**Replies:** 3\
**Last updated:** [March 11, 2019, 6:44pm UTC](https://discourse.paraview.org/t/dropping-support-for-os-x-10-11-el-capitan/1431 "2019-03-11T18:44:59Z")

</div>

Should we drop OS X 10.11 (El Capitan)? With Qt and OS X always being a finicky pair, I am trying to narrow down the combinations we support. Since Apple stopped supported OS X 10.11 as of August 2018, does it make sense…