Roots Magic 9 not working with MacOS Sonoma Beta 14.0

Has anyone encountered this problem. Opening Roots Magic 9 using MacOS Sonoma Beta 14.0 causes the program to open with an expanded screen which doesn’t allow access to details or the button to close the program or actually do anything. Only by doing a force quit can the program be exited.

I assume this is the Beta version of the forthcoming Mac OS. I have a vague memory of a post from some time back to the effect that RM doesn’t support Beta versions

1 Like

Thank You for Your reply and I will go forward

Mac OS 14 is far from ready for consumer use and it is unreasonable to expect rootsmagic to support it until released in October.Wait at least for OS version 14.2 or 3 before updating In January or February.

Thank You for Your reply and I will go forward

Yes, I am an Apple OS Beta user. Yes, RootsMagic does the maximum text size bug that is prevalent in earlier Mac OSes and also on PCs (caused by a font size bug) and the threads can be found by searching using SwissCows. What we are experiencing is a shortened version of the Settings so we cannot resize the screen after doing the Mac OS supersize options for the screen because those settings do not appear at all even after running the screen size variations in the Mac OS. I have used the Mac OS screen variations to some effect but the pallet does not shown when the screen is maximized pixelwize. Also the function key shortcuts for RootsMagic do not work as advertized. Yes, we are using the latest update for RootsMagic hoping thois issue can be resolved. I’ve beta-tested for RootsMagic for quite a few years. The thing is, if we see an issue using the Mac OS Beta then you can be sure others are also experiencing the same thing but not reporting it because they have given up. This has been going on for around a year so far. So it is not just the current the Mac OS Beta witnessing this odd behavior.

It would appear that when RootsMagic is opened, it defaults to maximum Font size and we cannot correct it on our end. Resetting to defaults also does nothing.

This is what we see >