sillsdev / sillsdev/ptx2pdf

Order of the elements on Basic page is unintuitive

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

Nobody has claimed this yet.

enhancement help wanted Python
Dominant language
Python
Stars
33
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Looks related to #669
Here's my usual workflow. Open ptxprint, start at the top of the Basic screen:
--Choose Project from the list (RTTT)
--Choose Book or Passage(s) I want to print (JHN 16-18)
--Choose Configuration... (DoubleSpForEditing)
--Print or head over to another page to tweak something first.

Oops! I didn't just print JHN 16-18; Ptxprint reverted to MRK 1-5, the Passage I was working with yesterday (with DoubleSpForEditing). , not the Passage I specified when I opened ptxprint just now. So P save this Config. with today's passage and print it. Now I also need to print 5 copies of the A5CheckerBooklet. Oops! The Passage reverted again to MRK 1-5, what I was working with yesterday.

I'm finding that nearly always I need to print today's Scripture passage Selection in more than one format, rather than more than one Selection in the same format. Add to this general workflow the physical location on the Basic tab, I find myself setting a passage and then a Configuration. It takes another mental step to set the Config first, and then go back and check the passage.

My preference would be that PTXPrint hang on to any new passage Selection I make, so it applies to a Configuration I select next. If I'm planning to work again with yesterday's passage that's fine; I will mentally approve that as I work down the screen. But if I choose a Configuration it seems awkward and annoying for the passage I just specified to disappear. I'm feeling like my aging brain needs all the help it can get! ;)

If it seems better to you to choose a Config first and then Select a passage, could the order on the screen be changed so Config is above Book/Selection? What do you think?

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 at the Basic page and compare the passage and configuration workflow described here with related issue #669. Done means the project retains the newly selected passage when another configuration is chosen, or the screen order reflects the decided resolution; verify that printing multiple formats uses the intended passage.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
design, desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.