Skip to main content

Mac Word: Save As Screen Too Big

Problem: The "save as" dialog box is too big for your screen and some of the options (such as new folder) and the resize corner are off screen, making things very, very, annoying.

Solution: Hit the 'shrink' button (up arrow) to see the abbreviated version of the "save as" menu. Then press that button again (now the 'expand' button). The dialog box now will fit the screen and you drag the corner to resize the dialog to a sensible size, which it will store.

From here.

Comments

  1. This just made it even worse. Now the top of the window is off the screen as well.....force quite time now!!!!!!

    ReplyDelete
  2. Many thanks! I have a MAC Air 11" and this saved me!

    ReplyDelete
  3. thank you!
    this has been annoying me for ages and I finally got around to googling it.

    so simple too. appreciate people like you who take the time to make our lives smoother.

    ReplyDelete
  4. Wowee. What an easy fix! Thanks so much.

    ReplyDelete
  5. Yeah, this just made it worse for me too, just like the guy above. Thanks tho...

    ReplyDelete
  6. just saved my life!!

    ReplyDelete
  7. Not working here. I've got a user who has this problem big time that nothing seems to solve. Clicking the "shrink" button in any Office program does shrink the menu down, but then when it's clicked again to "un-shrink", the Save As dialog expands again and the resize corner is way off the screen.

    FWIW, application menu bars also are way off the top of the screen, as if they're hiding under the Mac top menu bar. No way to access them (except via keyboard commands) and no way to grab the window's top so we can pull it back down to where it belongs.

    All of these things are Office 2008 specific. Other apps not affected.

    Any ideas?

    ReplyDelete
  8. Thanx! You've just saved me a LOT of irritation for times to come!

    ReplyDelete

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...