Display error on MacBook Pro (13") #1689

Closed
davidsivocha opened this Issue Sep 19, 2012 · 9 comments

6 participants

@davidsivocha

When opening brackets on Mountain Lion, the top menu inside brackets is half cut off making it difficult to read menu items and see the open file name.

This issue also applies when extended to full screen usage.

MacOSX Mountain Lion, 13inch display (non-retina)

@jasonsanjose jasonsanjose was assigned Sep 19, 2012
@jasonsanjose
Adobe Systems Incorporated member

Are you using the sprint 13 build with the installed www code or are you using a clone of the Brackets repo? A screenshot would help if you have an image sharing site or maybe Dropbox link that you can share.

@davidsivocha

Yep, using the sprint 13 build direct from this repo.

https://dl.dropbox.com/u/31397437/bracketsfullscreen.png
https://dl.dropbox.com/u/31397437/bracketsnonfullscreen.jpg

As you can see in both screen shots (using in both windowed and non-windowed mode) the top section where the menu and file name display is cut off somewhat in both instances.

@pthiess
Adobe Systems Incorporated member

Reviewed, marked medium priority.

@peterflynn
Adobe Systems Incorporated member

I think this is a dupe of #1147: on Mac brackets-shell, if the window size at initial launch is too small, the layout gets permanently stuck in a bad state.

@gruehle gruehle referenced this issue in adobe/brackets-shell Sep 26, 2012
Merged

Add fs.makedir() and fs.rename() APIs #120

@pthiess
Adobe Systems Incorporated member

Nominating to Sprint 15

@pthiess
Adobe Systems Incorporated member

Reviewed.

@gruehle gruehle was assigned Sep 26, 2012
@DennisKehrig

Note that in both cases (i.e. this one and #1147) it is not just the menu that is shifted to the top, it's the entire UI.
The current file indicator lines up perfectly with the bottom of the menu here. There just aren't any visual features above the file list that would make this more obvious.

@jasonsanjose
Adobe Systems Incorporated member

@davidsivocha The fix has landed from adobe/brackets-shell#125 but you'll either need to (a) wait for the sprint 15 build or (b) build brackets-shell on your own to confirm the fix. I've confirmed it myself, so I'll go ahead and close this issue.

@davidsivocha

@jasonsanjose Excellent, thanks, I look forward to the sprint 15 build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment