That bug has been fixed in v0.1.8; we’ll be releasing it soon.
Cool! Can get arounds it by changing the desktop's resolution to see the settings and changing them, but glad to hear it's been fixed.
