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
If you call ROT.Display() it only accepts arguments in characters, ie. specifying that the console should be X by Y characters (of the supplied font).
This is annoying, for example in the case that you want to go full screen at some resolution or other then back-calculate text width and height resolution to make optimum use of the available screen space.
If you manually set screen mode before creating a ROT.Display() instance then ROT.Display() overwrites the screen mode. If you set afterwards, then you wind up with ROT.Display()'s character resolution not matching the screen mode.
Not a problem for me as I am working around this by avoiding the use of ROT.Display() entirely and using a tile-based approach... but seems a pretty serious issue if others look to use this to do anything more serious than a quick hack.
The text was updated successfully, but these errors were encountered:
I agree, that should be easier. There used to be a scale option in Display, but I appear to have removed it by accident some time ago. I've added it back in 833bdcd
I'd like to add a setResolution, and pull the bits that would have to be re-called out of __init and into a separate function.
If you call ROT.Display() it only accepts arguments in characters, ie. specifying that the console should be X by Y characters (of the supplied font).
This is annoying, for example in the case that you want to go full screen at some resolution or other then back-calculate text width and height resolution to make optimum use of the available screen space.
If you manually set screen mode before creating a ROT.Display() instance then ROT.Display() overwrites the screen mode. If you set afterwards, then you wind up with ROT.Display()'s character resolution not matching the screen mode.
Not a problem for me as I am working around this by avoiding the use of ROT.Display() entirely and using a tile-based approach... but seems a pretty serious issue if others look to use this to do anything more serious than a quick hack.
The text was updated successfully, but these errors were encountered: