-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resizing presenternotes-windows #473
Comments
Thanks for pointing me to the As a last resort, I can use the same type of resizing bars as in the editor. |
Attached a suggestion as to how it could be done. As previously mentioned, CSS is not where I excel, so don't be too puzzled if there are details that don't make sense. But the zip-file should show how one could come from the current code to a code in which resize helps the user fit the pages according to his or her own choosings. The files in the main folder are created by Sozi. The "Test-presenter.sozi.html" file in the subfolder is revised to bring in the blessings of the resize-property. :) |
OK. It seems that My preference goes to an horizontal resizer between the left and right parts of the screen, and a vertical resizer between the top and bottom preview areas. I will upload a new preview release soon. |
Superb, @SENSHU !!! This is really good. |
@Sozi20.01:
I can confirm that two of the issues mentioned in Link are now fixed: It works in Chromiumbased browsers, and instructions for presenterview-formatting now pops up. Thank you very much 👍
In order to be really functional in live sessions, I do however, still believe that the "current view" becomes too small on the presenter screen. I've previously (link, suggested solution link) suggested that they become resizable through the "resize"-tag in css. The reason why I believe this solution to be superior is that it makes it possible for the presenter to adapt to his or her given hardware -- together with his or her preferences as to how many notes that are needed.
It's of course your choice :)
The text was updated successfully, but these errors were encountered: