I have an Interesting Problem

[kgschlosser]

I am in the process of writing a plugin. and what is happening is when i click on the apply button for an action it hangs EventGhost. but if i click on the test button all is fine.

if i run EventGhost in debug mode the apply button starts working again.

I am not sure if anyone has ever encountered this but I get no errors in the log or in the debug log file. and it only does it with this plugin. I have scoured my code and see nothing wrong. I would post the code but it is several thousand lines.

maybe someone could shed some light.

[Sem;colon]

Does it happen on any action or just one? Can you post the configure part of that action?

[kgschlosser]

I got it sorted. sorry i forgot to post that i got it working. I am using the Compile class inside of an action and i think it was having some difficulties when a traceback occurred in my exec code and it didn't know what to do. so i unbound the apply button and bound it to my own function that i has call the class without using the dispatchevent to see if a traceback occurred and if one didn't it would then call dispatchevent. I am still trying to figure one part of it, and just now i think i came up with the solution i just have to find the place to do it. i don't know what variable in the treeitem holds the actions args that way i can replace them and set the dirty flag.

the plugin really bends a lot of what EG does with python scripts. but great improvements. I would also love to know if there is a way to use something like inspect to comb through the eg __builtin__ to grab all of the classes and functions to build a code completion dict. it would take a very very long time to make one by hand.

it's a pretty cool plugin, i have to get the autocomplete working and then i will release it. i released a version for testing purposes. the version i am working on now sets a builtin called script that allows access to any script object created from anywhere inside of EG and also has the best traceback handling. it will ask if you want to open the script editor on traceback and then it will highlight the line that has the actual error. and it also allows for multiple dynamic files for each script. for code organization, I just have 2 bits left to tackle, the autocomplete and overriding the existing script actions that may have been created before the plugin was installed.

[Sem;colon]

Sounds very cool indeed, I'm looking forward to it!