Skip to content

Improve usability with configurable fonts, symbol search, and bug fixes - #469

Open
AbhiAgnal wants to merge 7 commits into
mortbopet:masterfrom
AbhiAgnal:feature/ripes-improvements
Open

Improve usability with configurable fonts, symbol search, and bug fixes#469
AbhiAgnal wants to merge 7 commits into
mortbopet:masterfrom
AbhiAgnal:feature/ripes-improvements

Conversation

@AbhiAgnal

Copy link
Copy Markdown

Summary

This PR contains several usability improvements and bug fixes for Ripes.

Improvements

  • Add search/filter support to the Symbol Navigator.
  • Add configurable fonts for:
    • Source editor
    • Executable code view
    • Register pane
  • Persist register display radix across sessions.
  • Generate a proper macOS application icon during the build.
  • Improve processor diagram readability.

Bug fixes

  • Fix executable code disassembly showing unknown instructions by decoding from the loaded memory image.
  • Fix save dialog source filename extension handling when the user already provides an extension.

Tested

  • macOS (Apple Silicon)
  • Qt 6

@mortbopet mortbopet left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR - a few comments.

Comment thread src/processortab.cpp
StageIndex sid = {laneIt.first, stageIdx};
auto *stagelabel = new vsrtl::Label(topLevelComponent, "-");
stagelabel->setPointSize(14);
stagelabel->setPointSize(16);

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

from one magic constant to another. I remember back when i developed this, i had issues with font scaling across different systems... Have you checked that this new font size for stage labels is reasonable on e.g. both Windows and Linux systems?

Comment thread src/ripessettings.cpp
Comment on lines +38 to +39
{RIPES_SETTING_EDITORFONT, QFont(Fonts::monospace, 11)},
{RIPES_SETTING_EXECUTABLECODEFONT, QFont(Fonts::monospace, 11)},

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you provide a compelling argument for why we need separate fonts for the editor and executable code? Allowing for changing the font is perfectly reasonable, but to avoid settings bloat, i'd wager on sharing a single font for the editor and executable code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants