Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ability to customize and remove headers for part problems #5

Closed
Strauman opened this issue Apr 5, 2018 · 1 comment
Closed

Ability to customize and remove headers for part problems #5

Strauman opened this issue Apr 5, 2018 · 1 comment
Labels
new feature New accepted feature
Milestone
Next release - 0.1.0

Comments

@Strauman
Copy link
Owner

Strauman commented Apr 5, 2018 •
edited
Loading

As of now, the \makeset[nohead]{}still makes part problem headers. If the author of the bank does not wish these, the author should be able to turn them off. Making new headers can still be done with \At\VeryBeginPartproblem
@Strauman Strauman added the new feature New accepted feature label Apr 5, 2018
@Strauman Strauman mentioned this issue Apr 5, 2018
Closed
@Strauman Strauman changed the title Ability to customize headers for part problems Ability to customize and remove headers for part problems Apr 5, 2018
@Strauman
Copy link
Owner Author

Strauman commented Apr 5, 2018

Links to #4

@Strauman Strauman added this to the Next patch - 0.0.7 milestone Apr 5, 2018
@Strauman Strauman added new feature New accepted feature and removed new feature New accepted feature labels Apr 5, 2018
Strauman added a commit that referenced this issue Apr 6, 2018
@Strauman
- Added package options:
daba4b3 
part problems on/off
tighten paragraphs true/false
problem header
part problem header
solution header
exercise directory

- Removed default exercise directory and prints hint in error if exercise file not found
- Deprecated \setExercisesDir and prints an error if this is used. \exercisebanksetup{exercise directory=directory} is superior

closes #4 and closes #5 and also affects #1

increased version number to 0.1.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
new feature New accepted feature
Projects
None yet
Milestone
Next release - 0.1.0
Development

No branches or pull requests
1 participant
@Strauman