Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debugger: Migrates Memory Search tab to it's own widget #10813

Merged

Conversation

Daniel-McCarthy
Copy link
Contributor

@Daniel-McCarthy Daniel-McCarthy commented Feb 14, 2024

Description of Changes

Moves Memory Search UI into it's own custom widget and migrates the search related functions from CpuWidget.h/cpp/ui to their own MemorySearchWidget.

Rationale behind Changes

The scope of Memory search related functionality is increasing and the CpuWidget is already fairly bloated being a general parent of a lot of different and unrelated functionality. This helps make CpuWidget easier to read/understand/maintain and allows the new MemorySearchWidget to expand in functionality and improve focus.

Suggested Testing Steps

This impacts all search related functionality, and integration between other components, such as double clicking an address and seeing it in Memory View, or visiting a search result in disassembly view, or taking a search result into saved addresses model.

Note:
Also makes the background color of the memory search widget a slightly darker color. The original color is set via witchcraft and sorcery and the new widget does not approve.

Moves the Memory Search fucntionality to it's own widget so as to not pollute the CpuWidget with search related functionality, especially as it is intended to grow in scope. CpuWidget is fairly general and as such everything tends to get tossed together which makes it harder to navigate/understand/maintain.
@refractionpcsx2 refractionpcsx2 merged commit ce5e66a into PCSX2:master Feb 21, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants