Re: Application window hidden under OSX menu bar

[Herbert Schulz]

On Apr 1, 2013, at 2:37 PM, Kirk Fickert <kirkf...@gmail.com> wrote:

> I'm not sure if this really is a BBedit bug or an OSX bug, but through some series of events I somehow managed to get my editing window "stuck". It won't move and the app window bar is hidden underneath the OSX top menu bar. Closing/opening the program has no effect. Once a window is open I can click, "Open in New Window" and a new window will appear and I can minimize, resize, move around that child window with no problems.
>
> The fix is to have dual monitors, turn on display mirroring and that will pop the window out. However, if you are like me at the moment and away from my desk and second monitor (MacBook Pro), it doesn't do a lot of good.
>
>

Howdy,

Can you go into Mission Control, select that window and then Close it with Cmd-W?

Good Luck,

Herb Schulz
(herbs at wideopenwest dot com)

[Christopher Stone]

On Apr 01, 2013, at 14:37, Kirk Fickert <kirkf...@gmail.com> wrote:

I'm not sure if this really is a BBedit bug or an OSX bug, but through some series of events I somehow managed to get my editing window "stuck".  It won't move and the app window bar is hidden underneath the OSX top menu bar.

______________________________________________________________________

Hey Kirk,

Operator error perhaps.  :)

This seems to happen a fair amount when people disconnect from their multi-monitor setup.

Search the list for "window stuck", and you'll discover that you're not the first to be bedeviled.

I started to suggest 'Zoom', but it seems to have been removed from the window menu.  (I think I knew that already but forgot.)

The easiest fix is to put a couple of Applescripts in your script menu and give them keyboard shortcuts.

-------------------------------------------

tell application "BBEdit"

set position of front window to {0, 44}

end tell

-------------------------------------------

tell application "BBEdit"

set position of every window to {0, 44}

end tell

-------------------------------------------

** I've posted quite a bit about positioning and resizing windows with Applescript.

--

Best Regards,

Chris

[Ted Burger]

Perchance did you switch to full screen mode, then position your document all the way to the top, then exit full screen mode??

Thanks,

Ted

***********************  Ted Burger  ****************************
t...@tobsupport.com      *********     www.tobsupport.com

--
--
You received this message because you are subscribed to the
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to bbe...@googlegroups.com
To unsubscribe from this group, send email to
bbedit+un...@googlegroups.com
For more options, visit this group at
<http://groups.google.com/group/bbedit?hl=en>
If you have a feature request or would like to report a problem,
please email "sup...@barebones.com" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
 
---
You received this message because you are subscribed to the Google Groups "BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bbedit+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Clay]

I run into a similar problem, in that none of my BBEdit windows are visible at all.  This occurs, as Christopher has indicated, when I disconnect multiple monitors.  I  am lucky enough that my employer has provided me with a new 15" MacBookPro with Retina Display.  It has a lot of video horsepower and I like to use real estate...so I have two SyncMaster SA850T monitors running at full resolution (each 2560x1440, one portrait and one landscape) and the MBP is running native resolution (2880x1800). The problem is: the BBEdit windows collapse to never never land.  The method described above seems to fix my problem.  It seems to *not* occur if I methodically remove the portrait then the landscape... then wait about five seconds, then close the laptop. 

The applescripts from Chris look interesting.  Chris, if you find a few minutes, would you mind writing a step by step for that process?  Your effort would be appreciated (at least by me :-).

Cheers,
Clay

[Ted Stresen-Reuter]

It's great to share information and I know for a fact that BBEdit support would *LOVE* to receive bug reports on this (rather than having to follow every thread on this list). Be sure to include all the detailed steps required to reproduce the bug and any preconditions along with version numbers. I've had nothing but experiences submitting bug reports this way.

Good luck and glad to hear you found a solution.

Ted

[Christopher Stone]

On Oct 16, 2014, at 17:48, Clay <clam...@instartlogic.com> wrote:

The applescripts from Chris look interesting.  Chris, if you find a few minutes, would you mind writing a step by step for that process?  Your effort would be appreciated (at least by me :-).

______________________________________________________________________

Hey Clay,

You mean these?

-------------------------------------------

tell application "BBEdit"

set position of front window to {0, 44}

end tell

-------------------------------------------

tell application "BBEdit"

set position of every window to {0, 44}

end tell

-------------------------------------------

Open the Applescript Editor on your machine.

Save each of the two scripts with a file-format of 'Script', and give them descriptive names like 'Reset Position of Every Window.scpt' and 'Reset Position of Front Window.scpt' (or whatever works for you).

Then use the Script menu in BBEdit to open the Scripts folder (3rd item down).

Move the scripts into that folder.

Use BBEdit's 'Menu & Shortcuts' prefs to assign them keyboard shortcuts, and you're good to go.

You can use similar scripts to resize and reposition windows on a specific monitor, but that a little more complicated.  Scope this out:

https://groups.google.com/d/msg/bbedit/A9lfXMOAn90/Jkgfc8mJt-AJ

Contact me off-list if you want to know more.

--

Best Regards,

Chris

[useEvil]

Thanks for the workaround.  But, this bug really needs to be fixed.

[Rich Siegel]

On Sunday, November 9, 2014, useEvil <use...@gmail.com> wrote:

> Thanks for the workaround. But, this bug really needs to be fixed.

Agreed. It's bug in the OS, reported as Radar 18810292.

R.
--
Rich Siegel Bare Bones Software, Inc.
<sie...@barebones.com> <http://www.barebones.com/>

Someday I'll look back on all this and laugh... until they sedate me.