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
Some slides don't fit on screens with smaller resolutions (for example, 1366x768), but there is no way to scroll them down. You can decrease the font size until the slide fits, but you cannot increase it again - hitting Ctrl-+ repeatedly only makes the logo and the arrows bigger, while the text stays the same.
The text was updated successfully, but these errors were encountered:
Before, we solved this by moving some of the text to be foldable (unideal, but better than nothing for now). Assuming we don't fix the CSS to be more responsive, can you give some slides this is broken for and I can try to recreate? Thanks :)
Sure! So I think it's most difficult in this slide, since there is nothing I can fold:
Then there are some slides where I can't see the whole slide once I unfold a comment. One can argue that this shouldn't be a problem since I can fold the text back before reading the rest of the slide, but for example here I suspect it might be hard for someone to memorize the parts of a function first and then look at the examples, after folding that definition back up:
Thanks! The real solution would be to fix the CSS so that we can scroll down, but I think this is quite hard atm. For the time being, folding away is the only real answer (I know it kinda sucks). The first one, however, is a problem. I'll give it a look and play around.
I wonder if we could make better use of the horizontal space. On the first screenshot we could have the two boxes side-by-side. On the second, a wider box might save a few lines.
Some slides don't fit on screens with smaller resolutions (for example, 1366x768), but there is no way to scroll them down. You can decrease the font size until the slide fits, but you cannot increase it again - hitting Ctrl-+ repeatedly only makes the logo and the arrows bigger, while the text stays the same.
The text was updated successfully, but these errors were encountered: