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
Firstly, let me say that I really admire the work you have done with Numbas and this extension in particular.
Reading both the Numbas documentation and the readme provided here, it took me quite some time to figure out some things I think would justify an inclusion somewhere in the documentation:
I struggled to find out where I can actually set the amount of marks for a question of the type extension (because these lack the "Marking settings"-option). We can use set_credits() under "Marking algorithm" in our custom marking algorithm, but I found no way to comfortably set the marks-parameter itself. What I did was include this.marks=4 in the "When the part is created" field under "Scripts" -- which works just fine but is a bit oblique/should be documented somewhere.
As far as I can tell, none of the demos provided here cover the creation of new objects by the students, which was something I needed in my example and for which I had to figure out how to use the exists( )-function properly. Maybe one such example should be included as well? (I ended up using something similiar to if(exists(app,"f")=true,if(definition_string(app,"f")=f_correct, ...), ...); - which works if you know what the name of the next object that will be created by the user is (in this case f). I still have not figured out how to do it without knowing that.
The text was updated successfully, but these errors were encountered:
Firstly, let me say that I really admire the work you have done with Numbas and this extension in particular.
Reading both the Numbas documentation and the readme provided here, it took me quite some time to figure out some things I think would justify an inclusion somewhere in the documentation:
extension
(because these lack the "Marking settings"-option). We can useset_credits()
under "Marking algorithm" in our custom marking algorithm, but I found no way to comfortably set themarks
-parameter itself. What I did was includethis.marks=4
in the "When the part is created" field under "Scripts" -- which works just fine but is a bit oblique/should be documented somewhere.exists( )
-function properly. Maybe one such example should be included as well? (I ended up using something similiar toif(exists(app,"f")=true,if(definition_string(app,"f")=f_correct, ...), ...);
- which works if you know what the name of the next object that will be created by the user is (in this casef
). I still have not figured out how to do it without knowing that.The text was updated successfully, but these errors were encountered: