MobileRead Forums - View Single Post

NiLuJe · 05-03-2015, 02:10 PM

@kaznelson: For eips's purposes, yes (same build as on most other newish FW 5.x devices, eips for some strange reason appears to rely on the virtual xres, cf. eips -i or fbgrab -v).

Note that given the size of a character block, and the size of the screen, that only squeezes in one single extra column, and one that'll be cut-off by the right edge of the screen at that (something that might be more noticeable than on other devices, because of the much bigger blocks for such a small screen than on previous 600x800 devices, which used much smaller eips blocks).

I don't care enough about this to make sure every single eips print in my scripts fits into 37 columns, so some messages will most definitely get cut-off on this device. But at least now they're actually shown, instead of trying to print them way off-screen

.
One solution would be to refactor the whole thing to split things over multiple lines when a string exceeds the column length, but, again, meh.

.

For everyone else, the actual usable screen estate is of course 600x800.

05-03-2015, 02:10 PM	#111
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@kaznelson: For eips's purposes, yes (same build as on most other newish FW 5.x devices, eips for some strange reason appears to rely on the virtual xres, cf. eips -i or fbgrab -v). Note that given the size of a character block, and the size of the screen, that only squeezes in one single extra column, and one that'll be cut-off by the right edge of the screen at that (something that might be more noticeable than on other devices, because of the much bigger blocks for such a small screen than on previous 600x800 devices, which used much smaller eips blocks). I don't care enough about this to make sure every single eips print in my scripts fits into 37 columns, so some messages will most definitely get cut-off on this device. But at least now they're actually shown, instead of trying to print them way off-screen . One solution would be to refactor the whole thing to split things over multiple lines when a string exceeds the column length, but, again, meh. . For everyone else, the actual usable screen estate is of course 600x800. Last edited by NiLuJe; 05-03-2015 at 02:25 PM.