Ad blocker detected:
Our software and support is 100% free. This website is not.
You can donate in 2 ways, by turning off your ad blocker or by pressing the Donate button.
************ NOTICE ************
UPDATE YOUR BOOKMARKS!!!
We have an issue that there is no way around as of yet.
I have done all I can to try and prevent this from happening.
We are going to be losing the .com, .org and .de domains.
We have not been able to contact the original author of EventGhost
(the person that owns those domains) to redirect them to the new web server.
I set in motion when we first moved a redirection from the old server to the new server.
I also put in markers so that search engines would see this change and update any pointers
they have. We still have the .net domain for the production site. and the .rocks for the test site.
For the past few months you have been getting redirected to the .net site if you used one of the 3
domains mentioned above. I just wanted to tell everyone so they can make any changes needed.
This is where you report any issues if you are running a beta version of EventGhost
To submit a possible bug report please follow this template
Version: 0.5 beta 2 (the version you are running)
Traceback: Traceback (most recent call last):
File "<SOME_EVENTGHOST_FILE.py>", line 10, in <module>
File "<SOME_EVENTGHOST_FILE.py>", line 4, in SOME_EVENTGHOST_MODULE
copy and past any traceback information from the log if there is no traceback put NONE
in the Event field you will want to put the event that was triggered just prior to the traceback occurring, if there is personal data put PERSONAL DATA if there was no traceback or no event triggered right before the traceback put NO EVENT
Description: if you have the ability to replicate the issue then put in here a description of what you are doing to create the problem.
Screen Shots: screen shots of the error and any events/macros/acrions that were run before the issue or screen shots of the problem
Files: any files that may be used to isolate where the issue is. something like the log.txt file would go here
if you provide the above information before hand it will greatly speed up the diagnostic process. we will not have to ask for the bits and pieces. And also having a well formatted Bug Report filled out will get answered sooner then the ones that aren't
Thank you, looks good!
I have one question though, why isn't it possible to resolve the plugins the Events come from? Or better, how can the list be populated? At the moment there is only a System and a <unknown> node.
topix wrote:Did you hit Enter after typing the event name?
No I didn't... How should I know that I'm supposed to hit enter?
After hitting Enter the OK button isn't greyed out any more, but I honestly didn't expect that you have to press Enter - why is that? Wouldn't it be better to activate the button whenever the Box is not empty?
-The Hint is missing that you can use also drag and drop to add events
Didn't knew or tested it
That's funny, I didn't know that as well
It's cool though and worth a hint.
I was referring to the Hint in the old add event dialog, which I guess is helpful to people that are new to EventGhost:
kgschlosser wrote:can we also drag and drop events from the logger to populate the list in the dialog??
What kind of question is that ?
Maybe, I did not understand it correctly.
However - the answer is: of course we can.
I've already used it in several plugins. As an example, I can give the Music Bee plugin (main plugin dialog) or Media Player Classic plugin (Show MPC menu action).