Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Multiple changes in Page Properties and Page Numbers are not saved together

Closed Beginner friendly
  • Is something wrong?
#167 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@jage9 is already working on this.

Since Oct 9, 2026.

  • #168 by @jage9 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
kotlin
Domain
desktop

Research direction

Start with the update calls in the Page Properties and Page Numbers tabs, where the issue says several updates are chained with short-circuiting ||. Commit bf3590c introduced this, so its diff is a good place to see the original intent. Reproduce by changing two settings in Page Properties and clicking OK, then check that both survive. Done means every changed setting persists after OK and Make Default in both tabs, with the update calls all run.

Written by the indexing model from the issue text.

Description

In BrailleBlaster 3.2.5 on Windows, changing several settings in Page Properties or Page Numbers only applies the first changed setting. Other changes silently revert. This affects both OK and Make Default.

Steps to reproduce:

  1. Open a document and go to Settings > Page Properties.
  2. Change the page size and toggle Interpoint.
  3. Click OK, then reopen Page Properties.

Expected: Both changes are retained.
Actual: Only the first changed property is applied.

The same problem occurs in Page Numbers when changing a page-number position and other options together.

The update calls in both tabs are joined with short-circuiting ||, so later calls are skipped after an earlier call reports a change. This was introduced in commit bf3590c on November 10, 2025, and is present in the release tags from 3.2.1 onward.

Dominant language
Kotlin
Stars
15
Forks
11
Avg merge
1d 20m
Merged PRs (30d)
17

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from aphtech/brailleblaster

All issues in aphtech/brailleblaster

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.