Qt Creator 16.x / File Locking Conflict with PTC Integrity (MKS) SCM

Hello everyone,

I'm encountering an issue with recent versions of Qt Creator (likely starting from 16.x and onwards) regarding persistent file locking, which is causing conflicts with our Source Code Management (SCM) system, PTC Integrity (formerly MKS Integrity).

The Problem: When a source file is open in Qt Creator, PTC Integrity's standard update/sync operation fails because it cannot modify the file. Windows Resource Monitor indicates that Qt Creator holds an open handle on the file, preventing other processes from writing to it. The error message is typically "Access Denied" or "File in use."

How PTC Integrity Works: PTC Integrity operates by:

1. Deleting the local file that needs to be updated.
2. Downloading and creating a new, updated version of the file from the server in its place (e.g., to update header comments, version information).

The Contrast with Earlier Qt Creator Versions: Interestingly, earlier versions of Qt Creator did not exhibit this behavior. They seemed to release file handles more readily, allowing PTC Integrity to perform its update operations without conflict. This suggests a change in how Qt Creator now manages or monitors open files.

Question: Is there a specific setting in recent Qt Creator versions (e.g., related to file system watchers, indexer, or general file management preferences) that controls this more aggressive file locking/handle holding behavior? Or is this an intended change in how Qt Creator interacts with the file system?

Thank you.