Window access via CMD-1 now hides Quicken if it was already in that window. (Q Mac)

crashmeister3
crashmeister3 Quicken Mac Subscription Member ✭✭

I quite often use CMD-1 to make sure that my main window is open in Quicken. Recently, typing CMD-1 now toggles Quicken visibility. This happens even if you click on the file name in menu 'Window'.

This should not happen.

Comments

  • John_in_NC
    John_in_NC Quicken Mac Subscription SuperUser, Mac Beta Beta

    Command+1 has always toggled showing/hiding the Quicken Window. I just confirmed in older versions.

  • jacobs
    jacobs Quicken Mac Subscription SuperUser, Mac Beta Beta

    Just to clarify: if the main window is not the foreground window, Command+1 brings the main window to the front; if the main window is in the front, Command+1 hides it. That's slightly different than saying Command+1 toggles the window.

    I often find I have a Quicken supporting window open on the side of my screen, with some other application window like Safari converting most of my screen, including the Quicken main window. So I like that I can click on the visible piece of a Quicken window and then press Command+1 to bring the main window to the foreground. And occasionally, if I have the Quicken window front and center but want to find something quickly in an email or website blocked by the Quicken window, I like pressing Command+1 to hide the window, then pressing it against to bring it back.

    And as @John_in_NC says, it's been this way since modern Quicken Mac came out 10+ years ago.

    Quicken Mac Subscription • Quicken user since 1993
  • crashmeister3
    crashmeister3 Quicken Mac Subscription Member ✭✭

    Thanks for the feedback. This is very strange as I have a script that used to do a CMD-1 and then click on update all accounts. It worked.

    After LOTS of changes (upgrade from Intel Mac to Apple Silicon, New MacOS, Reinstall of ALL software to get rid of bloat etc…) my script (now without CMD-1) no longer works in some situations. It works if it is run via launchd soon (tested with 5 minutes) after locking the screen. When left for a long period it fails. System settings have sleep turned off.

    Oh well, back to the drawing board…

  • jacobs
    jacobs Quicken Mac Subscription SuperUser, Mac Beta Beta

    @crashmeister3 If you want to make sure a script always works with Command+1, you could first make the script open a different window in Quicken, such as Window>Tags; then Command+1 will always take you to the main window whether it was previously visible or not.

    Also, if your goal is to run Update All Accounts, you can run a script to do Update All Accounts irrespective of whether the main window is visible or hidden; it will bring the main window to the front and run Update All Accounts.

    Quicken Mac Subscription • Quicken user since 1993
  • crashmeister3
    crashmeister3 Quicken Mac Subscription Member ✭✭

    The issue is when the Mac is unattended (Screen locked). When the Mac is unlocked, all works perfectly.

    My sequence is:

    Check to see if it's running, if not abort.

    Check to see if it's frontmost, if not bring to front.

    (OLD code) CMD-1

    Click 'Update all accounts'

    If was not frontmost, click 'Hide Quicken'

    Since the move to new Mac, CMD-1 started causing issues, so I removed it. Not quite sure how it worked on old system.

    If the Mac is locked (excerpt from my log file)

    2025/01/02 @ 22:30:16.559 QuickenUpdate: Before Front: false; Visible: true
    2025/01/02 @ 22:30:16.561 QuickenUpdate: Bringing to the front...
    2025/01/02 @ 22:30:17.583 QuickenUpdate: After Front: false; Visible: true
    2025/01/02 @ 22:30:17.671 QuickenUpdate: Account update started.
    2025/01/02 @ 22:30:17.672 QuickenUpdate: Quicken was NOT front app, will hide.
    2025/01/02 @ 22:30:19.182 QuickenUpdate: Error: Invalid index.

    Note that it never comes to the front so even though it says account update started, it did not. No error at that point. The error is when it tries to hide.

    At this point I'm going to go back to the old Mac and (if the update still works) add more log messages, to get a better view of why it does.

    BTW, I like your idea of opening another window, then CMD-1. This may be the key.