MinimServer Forum
Minimwatch 2 no icon - on Mac - Printable Version

+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: MinimServer 2 (/forumdisplay.php?fid=12)
+--- Thread: Minimwatch 2 no icon - on Mac (/showthread.php?tid=6049)



Minimwatch 2 no icon - on Mac - PhilE - 02-02-2021 18:26

Hi
I've just changed over to Minimserver 2. Before replacing version on rasberry pi I updated MinimWatch on my Mac (10.11.6). Installation worked ok and icon appeared in task bar with all property settings retained. After Minimserver on raspberry pi was replaced with version 2 the MinimWatch icon went pale blue. I exited from MinimWatch but when I tried to relaunch no icon appeared. As I hadn't downloaded latest java first time (as I thought I had it installed) I started from scratch with MinimWatch installation. However, icon still doesn't appear when I try to open MinimWatch. Advice on previous post (windows user) suggested icon may be in task bar overflow. Not sure if/how that applies on Mac.

Would welcome suggestions on how to solve this.


RE: Minimwatch 2 no icon - on Mac - simoncn - 02-02-2021 18:51

There is no task bar overflow area on the Mac.

Sometimes things get into a bad state on the Mac side of things, with a "zombie" instance running that blocks your attempt to launch any more instances. Logging out and logging in again should clean this up.

If this doesn't fix it, look in the minimwatch-out.log file in the ~/Library/MinimWatch folder to see if a launch error is reported there.


RE: Minimwatch 2 no icon - on Mac - PhilE - 02-02-2021 20:10

(02-02-2021 18:51)simoncn Wrote:  There is no task bar overflow area on the Mac.

Sometimes things get into a bad state on the Mac side of things, with a "zombie" instance running that blocks your attempt to launch any more instances. Logging out and logging in again should clean this up.

If this doesn't fix it, look in the minimwatch-out.log file in the ~/Library/MinimWatch folder to see if a launch error is reported there.

Logging out and logging in again did clean this up.

Thanks for your very prompt guidance.