Skip to content

Conversation

@0tkl
Copy link
Contributor

@0tkl 0tkl commented Jan 4, 2025

Same as arch1t3cht#145, just rephrase the commit message.

Stop hard-coding the font face and size of the crosshair coordinates (currently Verdana 12pt). Expose the options to the user and move the coordinates' current font settings to the default profile.

Developers need to be aware of the font size here when Hi-DPI support is about to be migrated to TSTools after Hi-DPI support is in master.

p->OptionAdd(tl_assistant, _("Skip over whitespace"), "Tool/Translation Assistant/Skip Whitespace");

auto visual_tools = p->PageSizer(_("Visual Tools"));
p->OptionAdd(visual_tools, _("Shape handle size"), "Tool/Visual/Shape Handle Size");
Copy link
Contributor Author

@0tkl 0tkl Oct 4, 2025

Choose a reason for hiding this comment

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

Looking back, I realized it's a redundant line that had been mistakenly cherry-picked from the original PR, leading to a fatal consequence that the preference dialog failed to open.

Stop hard-coding the font face and size of the crosshair coordinates
(currently Verdana 12pt). Expose the options to the user and move the
coordinates' current font settings to the default profile.
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.

1 participant