This whole experience has been nightmarish - I thought I had lost a week of work as I couldn't open my model, although stepping down to v15 is a life-saving workaround. If the software isn't compatible, that should be clearly stated on the website before one buys a license. It's not just early adopters who are hurt - it's also people buying a new system, which includes only the newest OS. That is the whole point of making the developer version of a new OS available first - to beta test as well as assure that the software will be ready to go on Day One. That's what a beta is.Īnd the problem is not the OS.it is the software that must be configured to run on the OS, not vice-versa. No, the public release of an OS is not like a public beta. I really, really don't want to have to let it go! However my A:M sub runs out mid January and I really hope that Hash could give us Mac users some solid info as to the future of the Mac version. The first release is always a bit like a massive public beta test of the new OS! Better to wait till Apple have released an update or two before joining in! Well I've never been one to jump strait onto a new OS update. Guess it's time to recode from scratch or else it seems the Mac version is dead. It isn't like the OS update was a surprise - beta versions have been available to developers for MONTHS. If the OS makes changes, you update the software. I just bought a second subscription for my other machine so I am quite pissed off. I refuse to believe the code can't be updated. Steffen said he can´t really fix that dialogue issue, it would mean to re-code a:m completely for the mac, and that there are several system files on apples list of things they intend to neglect in the future that are necessary to run a:m in the first place. however, i don´t know if v18 even works on mavericks. for the "save as", "import" menus and stuff it´s more convenient to use the old workaround, hide a:m and then go back to it, so the dialogue will remain open and be active after that. this has been a pain in v17, because it happenend a lot, and one couldn´t use the workaround of hiding a:m and then go back to it, because you were really stuck in that menu. that menue then just simply closes, and you can try again, hopefully with more luck this time. that´s mainly for the dialogue boxes within a:m, such as the edit cp-weights menu, or the options menu, things like that. whenever a menu is stuck, you can now press command "Q", to get out. it´s actually more of a workaround than a fix. I cant tell, dont have mavericks installed, but i also intend to.īut steffen added a "fix" for the menu dialogue issues in v18.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |