contrun
commented
1 year ago Your concern is vaild. I think there are two different use cases.
One is that the same person splits his/her presentation into different files and he/she want to presents them at once. In this case, he/she naturally wants a fluent transition (the features as you mentioned, no pressing Q and easily going back to previous file, are indeed desirable).
Another theoretical usage is that the many people present with patat in the same computer, or the same person gives a few lectures in the same day, and there are some breaks between the lectures. If so, they may want some kind of isolation between the sessions. I must admit the chance of this use case is slim. What I had in mind is the first use case.
I just thought giving people hints on the length of one file and requiring them to press Q to present a new file is acceptable. And it is quite easy to implement.
This seems reasonable and code looks good -- but I'd like to understand better what the use case is.
As presentations get lengthier, it can be useful to split them up over multiple files. But then I would also expect to be able to navigate back to earlier slides (e.g. when there's a question from the audience). Implementing this is trickier, since theoretically each file could have different settings, which doesn't really work well with the existing code.
Another thing that's a bit weird is that pressing Q does not quit immediately, but rather jumps to the next file.