## [ISSUE 22] [SEARCH_VIEW] Memory option for row, which was selected…

[svlad-90]

… during the previous search

1. [X] Have you followed the guidelines in our Contributing document?
2. [X] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
3. [X] Have you built the project, and performed manual testing of your functionality for all supported platforms - Linux and Windows?
4. [ ] Does your change introduce new interfaces?
5. [ ] Have you increased the version of the plugin?
6. [X] Is your change backward-compatible with the previous version of the plugin?
7. [ ] Does your functionality designed in a way to allow the execution of the unit-tests?
8. [ ] Have you developed unit-tests for newly developed functionality?

Change description:

• Addition of CTableMemoryJumper class
• Modification of CSearchResultModel to provide data, which is needed for the implemented functionality
• Addition of usage of the CTableMemoryJumper class into the CDLTMessageAnalyzer CDLTMessageAnalyzer

• ( side-work ) Normalization of paths within the installation guide

  Verification criteria:

Manual testing was done successfully on both Linux and Windows.

---

Were unit-tests executed?

• [ ] Yes

Unit-tests execution result: ____

• [X] No

Why? New functionality heavily relies on QT framework. No possibility to implement trivial UT to cover it.