The Ghost Dialog on macOS - Too Many Threads to Ignore

[Aaron Bourgoin]

While this is not nearly the issue that the Teamwork error messages represent, there are so many threads on the ghost dialog box now that I can't follow them all. It hasn't hit me for a while, but I haven't seen any word from Graphisoft that acknowledges the issue. Surely this is a bug fix on the near horizon.

If you have this problem, please do a search before pposting a new topic. We feel your pain.

PS. The BB won't let me tag MacOS as a label. I changed the Thread location, selected "Other".  :- )

Operating system used: Mac Apple Silicon Tahoe

[Lee Hankins]

This does seem to be widespread. I suspect Graphisoft are aware and looking in to it but it’s going to be challenging to track down. We’ve got 13 machines with at least 7 of them with the exact same hardware and specification and only two of them demonstrate this issue. The intel MacBooks with LG27’’ Ultrafine displays aren’t affected nor is the M1 MacBook with the same display but some of the MacMini M2’s with Dell 27’’ displays are affected where others are not. Maybe it’s a screen resolution issue when using a second display and dependent on which is designated the primary and secondary. 

Maybe Graphisoft need to reach out to those that have reported it and gather exact detailed specifications of each set up including OS and AC version, add-ons etc to see if there are any similarities. 

[Barry Kelly]

According to a recent post from another user, a fix is on the way.

https://community.graphisoft.com/t5/Report-a-bug/Bug-with-ghost-menu-backgrounds-sticking-around-on-...

Barry.

[Eduardo Rolon]

Heard that they are working on a fix.

If you want to duplicate the issue try the following:

What I heard is that it happens when you click on a menu and AC is not active.

So in the case of Enscape if you open the Enscape window and have it in front and then click on another menu item (including Enscape's) then you get the ghost menu.

---

https://community.graphisoft.com/t5/Installation-update/Drop-Down-Menu-UI/m-p/688983#M39158

I have been able to duplicate consistently using with the Enscape menu but not with other applications.

[Eduardo Rolon · Accepted solution]

See a more detailed answer at the end of this thread

https://community.graphisoft.com/t5/Installation-update/Bug-with-ghost-menu-backgrounds-sticking-aro...

---

@BulldogBen wrote:

Hi everyone, enthusiastic Noob here.

I've had the problem too, but I now know how to avoid it thanks to GraphiSoft Support. They also say they have a fix on the way. Here's the part of their response to me that was most helpful...

On single-monitor setups, this issue does not usually occur because the menu bar typically reflects the active application. However, on dual-monitor setups, Archicad’s menu bar may remain visible but inactive. This can be reproduced by following these steps:
 

1. Open Archicad on monitor A.
2. Switch to monitor B and open another application (for example, a PDF in Preview).
3. The Archicad menu bar on monitor A becomes grey and inactive.
4. Switch back to monitor A and click directly on one of the menus (e.g. View).

5. The empty outline of the View menu remains visible even after moving the mouse away.

This behaviour can be reproduced repeatedly by switching between monitors and clicking different menus. It affects all menus except Help.
 
As a temporary workaround, please avoid clicking on Archicad’s menu bar when it is grey and inactive. Clicking on any Archicad dialog box or window will usually make Archicad the active application again and restore the menu bar. Once Archicad is active, the menu bar can be used normally.
 
A permanent solution has been identified and is planned for inclusion in AC29.1.0-preview and AC28.3.3.

Looks like they have worked hard to reproduce it and a fix is on the way 🙏🏻 The reason it happened to me so often is I was watching a tutorial on one screen, then moving my mouse to ArchiCAD on the other and often going straight to a menu.

(I do have a nagging issue with Tool Tips stopping working which I though was related, but seems to be a separate issue)

---