Activity
From 01/14/2015 to 02/12/2015
01/15/2015
-
12:28 pm Feature #260 (Closed): answers in scientific notation (\AMCnumericChoices)
- Ive only taken a basic programming course, but I suppose I could give it a try. Where do I even begin looking into this?
01/14/2015
-
07:48 pm Feature #260 (Closed): answers in scientific notation (\AMCnumericChoices)
- If you have some LaTeX skills: look at the code for @AMCnumericChoices@, and extend it. If you do so, please propose ...
-
06:20 pm Feature #260 (Closed): answers in scientific notation (\AMCnumericChoices)
- I'm assuming this feature hasn't been implemented, but I absolutely need it. Is there any way for me to work around t...
-
05:07 pm Feature #338 (Closed): Help us avoid bad question identifiers
- > Yes, but I expect that in that situation it is not {question} which is used.
If @\AMCcode@ is not exactly what the... -
12:30 pm Feature #338 (Closed): Help us avoid bad question identifiers
- Alexis Bienvenüe wrote:
> > AMC to use such IDs internally
> In some situations (maybe to get some other codes), th... -
12:20 pm Feature #338 (Closed): Help us avoid bad question identifiers
- > AMC to use such IDs internally
In some situations (maybe to get some other codes), the end-user can also use this ... -
12:07 pm Feature #338 (Closed): Help us avoid bad question identifiers
- Hi Alexis,
Well, there are not "invalid", they are "reserved". And I do scope my question identifiers, I had:
... -
12:01 pm Feature #338 (Closed): Help us avoid bad question identifiers
- These are not _invalid_ id's. @foo.1@ and @foo.2@ are concatenated to build a @foo@ string. For example, this is used...
-
11:47 am Feature #338 (Closed): Help us avoid bad question identifiers
Also available in: Atom