Go to Next Slide / Go To Previous Slide in Course Presentations
Submitted by febster on Tue, 02/28/2017 - 07:04
Forums:
Hi there!
Just thought this would make life a lot easier.
https://screencast.com/t/gipQlDlX
Basically, it's just a request in course presentations in the 'Go to Slide' functionality to have a dropdown menu in which you could select a 'Go to next slide' and 'Go to previous slide'. This would eliminate having to correct other slides that occur after an inserted slide. Would certainly save a lot of time. Don't know if others would find this useful.
Many thanks!
Timothy
Summary:
Go To Slides
Content types:
Issue Status:
fnoks
Tue, 02/28/2017 - 08:50
Permalink
Hi,This sounds like a useful
Hi,
This sounds like a useful feature. Let's hope one of the developers in the community picks this one up :)
nmillin
Mon, 03/13/2017 - 15:48
Permalink
I took a first pass at this.
I took a first pass at this. You can view the pull requests at https://github.com/h5p/h5p-course-presentation/pull/40 & https://github.com/h5p/h5p-editor-course-presentation/pull/8. The code needed for this is split between the Course Presentation & Editor Course Presentation libraries.
The default is for the field to be blank, but if someone chooses next or previous it will override the jump to number value. The Title can still be used, but if it is blank the title will be set automatically (ex: "Go to next slide" or "Go to previous slide").
I had trouble in the arrangement of the fields. If I had the new field ('nextPreviousSlide') above invisible, the metadata field would populate the label and description of the field. I looked into this, but couldn't figure out why H5PEditor.findField (path, parent) was returning this. Maybe something to do with metadata field being deprecated?
Anyways, let me know what you think. Thanks.
-Nate
falcon
Wed, 03/15/2017 - 09:45
Permalink
Great Nate!Will follow this
Great Nate!
Will follow this up on GitHub. Probably later today.
Sindre Bøyum
Tue, 02/23/2021 - 10:42
Permalink
This feature request can be
This feature request can be closed