EventGhost

GBWebmaster wrote:But what can I do, that EG not connect MM automatically at the start of EG?
MM should only start, when I want to hear my music ...

I'm sorry, but I probably did not understand what is the problem?

Pako

Hello Pako,
the problem for my system is, that MM starts with EG. With the exit-command after on-init I can close MM, but sometimes MM fail to respond past the exit command or some processes prevent the MM-stop.
Therefore, it would be better, when the connect between EG and MM only then start, when I want to use MM.

Do you know, what I mean?
Sorry, but my English is strongly limited ...

GBWebmaster

Pako, I can confirm this problem that GBWesbmaster is talking about.

I just installed the new version of this plugin. When I start eventGhost MM4 is started as well. This is not what we want. The old version of the plugin did not do this.

Please take a look at this when you get the chance. I hope I can find a copy of the old plugin to use until this can be fixed...

to be safe, this is the version that I am talking about: https://eventghost.svn.sourceforge.net/ ... _init__.py

Well, I'll think about it and perhaps find a suitable solution.

Pako

Is it registering for events that is causing the problem? If so, can't you move that code into the connect command, instead of doing it when the plugin first loads?

What I have done in VoxCommando is to auto-connect to MM, but only when the user issues a command to MM. At that point, I also register for events. This way when they start VoxCommando MM does not start. They won't receive events from MM either, but as soon as they issue any command to MM they start to receive events.

jitterjames wrote:Is it registering for events that is causing the problem?

Yes, that's the reason.
But never mind, I think that somehow I might solved.

Pako

Here you have a small Christmas gift.
Plugin now automatically connects and disconnects the MM through ActiveX/COM.

jitterjames wrote:What I have done in VoxCommando is to auto-connect to MM, but only when the user issues a command to MM. At that point, I also register for events. This way when they start VoxCommando MM does not start. They won't receive events from MM either, but as soon as they issue any command to MM they start to receive events.

Yes, I understand. But this solution does not satisfy me. It has one big disadvantage. If the user controls MM directly (without using EG), events are not triggered.
Pako

then why do you have a "connect" command?

jitterjames wrote:then why do you have a "connect" command?

It is your mislead, I do not have this command.
I have only "Start" command.

Pako

I don't know what it's called but that is not so important. What does the start command do? It seems that the plugin starts itself automatically anyway. Why not let the user choose when to connect? How would this be a flaw?

The action which was formerly known as the Start/Connect MediaMonkey is now called Start MediaMonkey.
This allows you to start MM using EG (eg using remote control). But it's not a requirement. MM you can run any other way too (even manually).

Pako

it's fine. I will just keep using the old version of the plugin, which is great for me. Thanks.

jitterjames wrote:What I have done in VoxCommando is to auto-connect to MM, but only when the user issues a command to MM. At that point, I also register for events. This way when they start VoxCommando MM does not start. They won't receive events from MM either, but as soon as they issue any command to MM they start to receive events.

Pako wrote:Yes, I understand. But this solution does not satisfy me. It has one big disadvantage.

jitterjames wrote:I don't know what it's called but that is not so important. What does the start command do? It seems that the plugin starts itself automatically anyway. Why not let the user choose when to connect? How would this be a flaw?

Oh, I still owe you an explanation.
For what purpose actually is an event that is triggered by MM?
For instance, I use the event MediaMonkey.Play to display a notification. This works even if I control the MM manually (and it's mostly).

It is now clear? It's something wrong with this solution?

Pako

what solution?

jitterjames wrote:what solution?

This current (version 0.3.1):
1. MM will not start at plugin start
2. Connection EG-MM is automatic
3. No matter which way is MM launched or stopped. At any moment, events are triggered by MM and as well as at any moment can be MM controlled by EG.

Pako