Mac OS High Sierra 10.13 and Axoloti

[keyman]

From this user point of view all seems good/working as expected.
Using your @thetechnobear topics

Tested with: MBP / 10.13.0 High Sierra / Axoloti 1.0.12
Overall: No issues encountered

• Axoloti Firmware upload - ok
• Axoloti UI - compile, upload, run patch, adjust parameters - ok
• Axoloti Patch Editing - move objects, delete, move wires, add objects - ok
• Axoloti Libraries - sync , see objects - ok

• CPU - appears to be same as 10.12, as far as i can tell.

• memory - maybe a bit (tiny) more??

[hnzz]

Hei,
I have an empty menu bar on 10.13.
Only 'axoloti' appears but no file, edit, view, patch,....
(shortcuts do work)
Any way to fix this?
thnx

[keyman]

weird? Besides the "normal advices" - try re install axoloti? do you have the axoloti runtime installed?

Common installation problems

So we are starting to get some experience of users installing Axoloti, this thread will detail some common issues and suggestions if you have issue. (note: Im not going to include, pre-release/prototype boards - only production boards with 1.0 firmware) Read the relevant installation guide. I know, Im guilty of not reading installation/user guides - but Axoloti is a little different it IS worth it. It will get you up and running faster, and if your turning to this thread, because you have…

Can you give more info?? - previous macosx? - MBP??

[hnzz]

Hei Keyman,
I did a fresh OSX upgrade from 10.9
(i better didn't )
on a 13" MPB early 2011 / 4GB RAM.
Axoloti always worked well on this machine.
Oh I also installed the command line thing but not Xcode.

[hnzz]

[thetechnobear]

this appears to be a known bug in the openjdk (or java generally?)

see : https://bugs.openjdk.java.net/browse/JDK-8188085
( we use apple.laf.useScreenMenuBar = true)

can you both check to see which versions of Java you are running.
as Im not running 10.13, i cannot tell you if this is just the openjdk or also an issue with the oracle release.
(Id generally recommend the oracle release of java)

some good news, the above bug report seems to indicate Apple are aware of the issue and looking to fix... though of course, no timeframe on it.

note: overall, whilst its great if 10.13 doesn't have issues, Id generally advise to hold off upgrading for a little while yet, there is still a bunch of software that has gremlins... (which is why Im holding of)... Id probably wait a couple of months after release, or ~ 10.13.2, and when major software developers are all claiming full support for it.

EDIT: bit more digging, on one forum, they said this was present in the dev beta releases of 10.13 in July... so id assume reported then... also it only effects later updates of Java 8. SO..this could mean @keyman happens to be on a slightly older version of Java and hence is not affected.
(so potentially rolling back to a previous update may fix it)

@johannes we will need to monitor if/when Apple is fixing this, if it drags on then we will probably need to 'hack' a 1.0.12 release which puts the menus on the frames (i.e. does use apple.laf.useScreenMenuBar when 10.13 is present )

[hnzz]

Thanks for help everybody:
It works after entering:

defaults write Axoloti AppleLanguages '("en-US")'

in terminal.