You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The code above is derived from the current documentation and works. This is slightly difficult to work with, since you have to remember two formats for specifying titles and exercises. Is it possible to have:
This is not directly related to the other issue. It as been the case since the first Version.
If you don't use an the Syntax of = inside the optional argument for the subtask it was always be different.
An option would be to add a second optional argument, like
\begin{subtask}[credit=x][title]
but this would lead to an issue if there is only one argument.
That's why I chose to create it that way.
To have the complete identical Syntax for both, would also be annoying for some, because in most cases (as far as I saw it) subtasks won't get a title.
What I can offer, is the possibility of making the task to use both variants
With a bit more effort, even with the removal of the empty group. But this might also confuse users.
The only possibility to get everything working would be to require the title but make a variant without a title as well. I will think about this, though I would not really like to change the default, but add a
subtask* which required the title...
This would define an extra environmet. Alternatively you could redefine subtask, replacing the first line of the Definition by \RenewDocumentEnvironment{subtask}{om}{.
The code above is derived from the current documentation and works. This is slightly difficult to work with, since you have to remember two formats for specifying titles and exercises. Is it possible to have:
work in an identical fashion to keep the format consistent? Currently, the title of subtaks is not rendered when the environment is set up this way.
This is probably related to recent fixes due to #176 .
The text was updated successfully, but these errors were encountered: