Edex-ui: Last line cut off on 1.1.1

[jajaperson]

Kind of similar to #291 . After upgrading, overflow no longer was visible, but the bottom line on the terminal (e.g. the vim command line) is hidden underneath the keyboard/file system bar.

System: MacOS Sierra
Shell: bash

[SerpentChris]

The same thing happens with 1.1.1 in Mojave for me.

[akbiggs]

I'm running into this issue too. This problem seems to go away if I change the number of rows set in the fix for #291 from "rows+1" to just "rows" here, but I've only tested on OS X currently. I'll build and test with my Windows laptop tomorrow.

@GitSquared What's the reason for this resize, and why "rows+1" instead of "rows"? Should there be a comment to explain what's going on there?

[GitSquared]

@akbiggs It's a bit of a hack because xterm.js' fit addon tends to cut smaller than the actual available size.

I'm wondering if the bug isn't related to you guys having a different screen ratio than 16:9 (i know some macOS devices use 16:10 or whatever), could you confirm this? @SerpentChris @jajaperson

[akbiggs]

Yup, you're right. I'm on a 16:10 display. I'll try hooking my laptop up to a 16:9 display and see what happens.

[GitSquared]

@akbiggs All right. If you confirm that it works as intended on 16:9, i'll make a workaround for this by testing the screen resolution before applying this "fix".

Mind if you give me the exact screen res of your 16:10 display?

[akbiggs]

2880 x 1800

Thanks so much for the speedy responses! This is super cool!!!

[jajaperson]

I'm on a 1440 x 900 (16:10) display.

[GitSquared]

@akbiggs Could you confirm the fix is working?

[fsegouin]

Having the same issue on a 3440x1440 monitor.

[eimantasbucys]

Same issue, using 1.1.2 on 1920x1080

[ask-compu]

Having this issue in Ubuntu 14.04 in windowed mode
Screenshot
Seems to be fixed if I resize the window in a certain way
Screenshot 2

[GitSquared]

@ask-compu This is because only a few aspect ratios are supported by eDEX and the windowed mode isn't locked to any of those. I opened #413 to address this. Thanks for the screenshots.