TASEmulators / TASEmulators/desmume

Request: Ability to Copy RAM Search Results

Open
#249 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement winport
Dominant language
C++
Stars
3.6k
Forks
646
PR merge metrics
No merged PRs in 30d

Description

Hello again. RAM searching is a popular feature for debugging purposes, however one important feature is missing from it, that is the ability to copy however many addresses (with the values respectively in each) you want so you can paste it somewhere. The Cheat Search feature has a feature similar to this where it allows you to copy the offset and value for cheats, though you can only copy one address at a time (that's kind of a let down when I prefer bulk testing). RAM search doesn't have a copy feature at all, I feel it could benefit those who want to test out however many offsets they please, maybe make it so we can copy more than one address at a time to (basically bulk copying, we can already do bulk elimination), this would greatly reduce the time needed to test a certain amount of addresses. Thanks again!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the RAM search interface and the existing Cheat Search copy behavior. Determine how RAM results are selected and how clipboard output is handled; done means allowing multiple selected addresses to be copied with their corresponding values for pasting elsewhere.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.