v5.14.0

[richardwilkes]

New Features

• The Reaction, Condition, Melee Weapon, and Ranged Weapon blocks on the character sheet no longer show up if they have no content.
• Added settings for the default PDF, Markdown, and Image scaling percentage to use (Feature Request: setting to adjust default pdf zoom level #723).
• Added a setting to auto-fit PDF content to the available space (Auto Fit to Window #692).
• Talent / Magery learning time reductions can now be accounted for in the study tracker (Account for talent/magery learning time reductions #655).
• Enabled deep-searching of files in the Library Explorer (Library-level equipment and advantage search #599). Note that which types of files are actually opened and searched are controlled in the Settings menu. If you have a slow hard drive, you may want to only enable a few types.
• Added menu items for moving equipment between the Carried and Other equipment lists (Feature request: move to x equipment in context menu #717).
• Added the ability to copy point record entries to other sheets (Feature Request: Ability to copy point record entries to other open character sheets #725).
• The various types of trait containers (i.e. the ones that aren't just a standard grouping) now have a visible marker that shows up in the list. As part of this, I also renamed the "Race" container to "Ancestry" to be consistent with the Ancestry capability.

Bug Fixes

• Markdown files that have Windows line endings in them can now be opened (Markdown Files Not Opening* #720).
• Techniques that have unsatisfied prerequisites will now have a unsatisfied_reason field in the save files (unsatisfied_reason does not appear on skills/techniques that have unsatisfied prerequisites #721).
• When updating the display, GCS now always resets the OpenGL state. This change was made to (hopefully!) fix the problem where some software would change the OpenGL state that GCS was using and not restore it to what it was previously. In particular, doing screen sharing using Discord to show a GCS window would often result in an unusable text display on the Windows platform. I've not been able to reproduce the problem myself, so I'm unclear if this actually fixed anything. If you have experienced the problem in the past, I'd be interested in hearing whether this worked or not.

---

This discussion was created from the release v5.14.0.