Currently, the most common projector resolution of 1024x768 pixels is hard-coded. Actually, it is only hard-coded in one place, so this would be trivial to fix, but we also need to check the rest of the code to be free of absolute pixel sizes – for instance, the overview margins etc., and the API for adding content come to my mind. However, in most places, I should have kept resolution-independence in mind already.
The resolution could be made configurable, but maybe it should be detected from the presentation screen. (On the other hand, this affects pre-rendering, which one would not want to perform with the final monitor configuration in all cases.)
Finally, the cache format (or filename scheme) needs to be adapted for multiple screen sizes.
This is much improved now. Most of the code should now properly deal with window and frame sizes at runtime. Only the initial rendering step itself uses the fixed resolution.
Currently, the most common projector resolution of 1024x768 pixels is hard-coded. Actually, it is only hard-coded in one place, so this would be trivial to fix, but we also need to check the rest of the code to be free of absolute pixel sizes – for instance, the overview margins etc., and the API for adding content come to my mind. However, in most places, I should have kept resolution-independence in mind already.
The resolution could be made configurable, but maybe it should be detected from the presentation screen. (On the other hand, this affects pre-rendering, which one would not want to perform with the final monitor configuration in all cases.)
Finally, the cache format (or filename scheme) needs to be adapted for multiple screen sizes.