Vector35 / Vector35/debugger

Use render layer to provide useful informaiton to the user

Open
#713 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Impact: Medium UI
Dominant language
C++
Stars
331
Forks
33
PR merge metrics
No merged PRs in 30d

Description

This includes:

  1. Register/variable values
  2. Branch predication

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 render layer named in the issue and reviewing how register/variable values and branch predication are currently represented. Define the user-facing information required for both items, then verify that the render layer presents it clearly.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
devtools, reverse-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.