FileMaker Pro 17 Advanced (184.108.40.206) becomes unresponsive (beachballs) as soon as the Script Workspace is opened. This occurs on Mac OS Mojave 10.14 Beta2 (18A314h).
Running Mac Pro (Late 2013) 64 GB Ram.
Happens every time.
You are running a beta OS. This is not an issue with FileMaker.
The two are not mutually exclusive nor is it necessarily a piece of information that the developers do not want to hear. On the contrary, I'd like to know if my software was not ready for an upcoming OS, and I'd like to know as early as possible!
I totally agree... and on a side note opening the script workplace has always been surprisingly slow even on fast machines... so definitively something has always been wrong...
I always try the beta versions in a secondary Mac and always with a new version Filemaker has problems.
Of course you can say its a beta but the problem is that when the final version is released always you see a message from filemaker don't update yet.... and of course all the clients update as soon as the final release is out there. And the problems begin.....
Any further information already available about older versions of FM like 16 to 13 and runtimes?
well, filemaker 15 seems to work fine!
(script manger and mainly the define buttons or button bar that causes filemaker 17 to crash)
The users don't seem affected in filemaker 17 also the problem is for the development. All the databases I tested in filemaker 17 in Mojave from the part of users are ok.
Retrieving data ...