Exercise order in grading tables using xsim and collections

Question

I'm trying to build exam sheets with xsim using collections where exercises doesn't show up in the id order.

The exercises print in the specified order (= counter order) in the exam itself but in the id order in the grading table which can be confusing.

Here is a MWE:

\documentclass{article}
\usepackage{xsim}

\DeclareExerciseCollection{test}
\xsimsetup{
  print-solutions/headings=false ,
  collect
}

\begin{document}

\gradingtable

\begin{exercise}[ID=one,points=3]
  Exercise one.
\end{exercise}
\begin{solution}
  Answer one.
\end{solution}

\begin{exercise}[ID=two,points=7]
  Exercise two.
\end{exercise}
\begin{solution}
  Answer two.
\end{solution}

\begin{exercise}[ID=three,points=1]
  Exercise three.
\end{exercise}
\begin{solution}
  Answer three.
\end{solution}

\printexercise{exercise}{one,three, two}

\end{document}

Here is what I get:

And here is what I would like to have (exercises 2 and 3 are switched in the grading table):

As far as understood from the manual of the package, xsim only include build-in functions to sort exercises by Type then ID or by ID. I've tried to dig in the source code of the package to build a function to sort exercises by counter but it's beyond my present abilities.

Is there a build-in (or an easy) way to do so that I overlooked? Otherwise, have you an idea of how to get it?

Answer 1

The reason for this is that the exercises are set up or defined in the order they appear even if they're not printed immediately. This defines properties like id or exercise-body and so on.

Some properties are first set when the exercises are actually printed, such as the exercise number.

The default templates for the grading tables use \ForEachUsedExerciseByType{} to loop through the exercises which uses the order in which the exercises have been defined.

At the moment there is no easy way to loop through the exercises in the order they have been printed. IMHO this is worth a feature request. I opened your issue on github for this again.