I just recently attended the Lectora Fundamentals and Lectora Intermediate classes with Interactive Advantage, so I’m a still a bit new to Lectora. In these classes, I was advised that the default page size 1099 by 662 is what I should use for desktop training. I’m curious if this is what you guys tend to use for non-responsive projects intended for desktop e-learning. I did add the full-width library object though if that makes a difference (still using the default page size of 1099 by 662). Would it make sense that I have some white space at the bottom of my training module though? I’ve attached a screenshot below for an example. It seems to show up in several monitor sizes and even a standard laptop resolution if I do not have the browser fully maximized.
Perhaps I’m a bit clueless, but I can’t really figure out why this white space would display if that not part of the development space provided for this page size…
Under the Publish options tab “HTML Options”, you can check the box to ‘Scale content to fill Window’. Does that solve the issue for you? (note, this won’t appear in the preview, but once published and viewed from the published content)
(The white space may just be the extra browser space outside of your actual module dimensions?)
If you already have the checkbox selected to scale the content, then maybe this just has to do with the width of your page – if you make that wider (manually drag it out) does the white space at the bottom go away?
Ahhh, good solution on the fill to browser when publishing. Thanks! I was only looking at “Preview in browser” and “Preview.” Manually clicking and dragging the window to be smaller than the maximize browser size does in fact eventually make that white space disappear. Should I not worry about it then? Is this something you have ever noticed in Preview mode?
Right – preview mode doesn’t give you the same option as the publish option to scale the content.
On a side note – the way I prefer to work (when using the scale content feature especially), is to leave in some padding around the edges. depending on how this opens from your LMS, it may butt right up against the top of the browser for example, which to me feels awkward.
This option also solves the way it looks in preview mode – so if you use a background image something like my screenshot, then you effectively have your borders around your module.