adbcc48de7
<!-- Please provide as much information as possible about what your PR aims to do. PRs with no description will most likely be closed until more information is provided. If you're planing on changing fundamental behaviour or add big new features, please open a GitHub Issue first before starting to work on it. If it's not something big and you still want to contact us about it, feel free to do so ! --> ### Problem description This PR aims to address #1645 that caused the built in file provider's change monitor to trigger the notification popup dialog multiple times in a row after multiple external file changes. ### Implementation description I added an additional boolean field `m_changeEventAcknowledgementPending` that tracks whether there are any pending or unacknowledged change notification dialogs to prevent further dialogs from being opened. The flag is only reset to its initial value once the user has acknowledged the first `PopupQuestion` dialog. Since the file is reloaded only after the user clicks 'Yes', it is unnecessary to ensure that only the latest popup is acknowledged. |
||
|---|---|---|
| .. | ||
| undo_operations | ||
| base64_provider.hpp | ||
| disk_provider.hpp | ||
| file_provider.hpp | ||
| gdb_provider.hpp | ||
| intel_hex_provider.hpp | ||
| memory_file_provider.hpp | ||
| motorola_srec_provider.hpp | ||
| null_provider.hpp | ||
| process_memory_provider.hpp | ||
| view_provider.hpp | ||