Could we expose more informations about QuestionSet?

[cornelles]

h5p-question-set/js/questionset.js

Line 138 in ff1fb3a

var initialParams = $.extend(true, {}, defaults, options);

I would like to be able to add an event on the start button if the introPage is enabled, for this I would need to expose the button, initialParams or params to get details about configuration of the QuestionSet.

What do you think?

[icc]

Could you provide an example of what you'll be using it for?

At the top of my head, it sounds like triggering a custom start event on the question set it self might be a better idea but it really depends on the use-case.

[cornelles]

Not the event is my problem, the problem its actually object definition, the QuestionSet, I want to add semantics to the object, lets say a checkbox, and my logic, where I process the event, will be dependent on that checkbox value.

[icc]

Which platform are you on? All platforms should offer a hook or action that allows you to modify the semantics (recipe of the editor form).

Check out the Hiding/disabling fields from the authoring tool section for an example: https://h5p.org/documentation/for-developers/authoring-tool-customization

[cornelles]

I'm using drupal 7 and I can add the semantic, the problem is in the scope of the callback I get access to H5P.QuestionSet which doesn't expose the "options" where my semantic value is, or maybe I'm handling this wrong.
https://h5p.org/events - I've played a little with resize event

Another example its like in drag-question
https://github.com/h5p/h5p-drag-question/blob/master/src/drag-question.js#L26
where they expose "options", I was expecting to have something like this in question-set too

[icc]

Ah, I'm not sure why this is hidden for Drag and Drop. You only need the custom value you've added and not to change it?

We're hoping to be able to provide a plugin API soon that will make it easier to override stuff.

[cornelles]

Answering your question; Yes!
Having the plugin api; it would be lovely :)

[icc]

A bit of an ugly hack, but to get it working right away you could try accessing the H5PIntegration.contents object. The parameters should be stored there as JSON.

[cornelles]

Thanks for your reply @icc
I have already made a workaround for this, I opened this issue just for a nice to have thingy