ThomasBott

... Or something with the SMTP settings is wrong. I was also wondering that no one registered in the forum for a long time, do I just tried to change...

@WoLpH There are already several plugins (like webserver or TCP events etc.) that allow bidirectional communication - so the simple approach is already in place. (single server currently)

Yes, I also wouldn't focus on compatibillity with old EG versions too much. Users should use the latest version of EG, so maintaining a maxVersion should be enough. We could...

> Unless the compatibility metadata specifically indicates incompatibility, I think EG should only give a warning message/confirmation dialog("This plugin may not be compatible with your EventGhost version, do you still...

> I think the K.I.S.S. it method is best for this feature. Did I get something wrong or did you suggest to keep it simple after suggesting to run a...

> It provides them with information on the probable cause for the issues they experience after installing an incompatible plugin. That can reduce support requests to plugin and EG developers....

> Yet another option for metadata format would be compatibility flags uuh, I like that one! It's easy to read and EG version independend! But if we go for it,...

> the plugin developer don't has to lookup the needed flags That could be solved by displaying the flag(s) that cause the incompatibility "alert" in the plugin chooser dialogue (e.g....

Orange is sometimes hard to distinguish from red if there is nothing on the screen that is red (I have seen applications in which red looks very orage) What about...

Very nice, sounds all very logical and useful to me - I'm very curious about the "running each event in it's own thread but with backwards compatibility" thing. It sounds...