Just wanted to keep everyone informed
Posted: Wed Apr 05, 2017 2:28 am
We are hopefully going to release the last beta of EG within the next week. It is more like a Release Candidate But we are going to cap adding any new features at this point. But we will be making changes if any bugs are found.
So if you are one of the people that are running the beta version and have discovered a problem. Then please share it with us so we can get it right before the full release. There is an infinate number of devices and setups so we can't test everything. Even tho we sure do try. So you beta testers are our front line to getting things resolved.
On another note.. We have Set the groundwork for EG 0.6 and this includes things like
This will be the biggest change you will see. I have been working on this for a couple of months now. But i have managed to code in a way to have each event that comes in to be run in it's own thread. so no more of having to wait for one macro to finish running before another can run. Now the real trick to this was how to make it backwards compatible. I have gotten a rough draft done up. The next trick was how to handle the logging aspects of it. and I came up with a nifty solution. and that was to make the main log only contain events and if you double click an event it will drop down to another log that shows everything that has taken place for that event. But this is going to add yet another feature (this can be enabled or disabled) But you will have the ability to access something like payload data for an event that has fired after other events have been run. this is nice for things like device states. or checking the last time an event was triggered. and you will no longer have to worry about running a polling loop in a python script WooHoo! all the threads that are created will be daemon threads. what this means is that if you close EG the threads will get terminated as well. I still have a couple of things i need to address with it like sending a notification that EG is closing. so that if a polling loop is for a network socket instead of just terminating and possibly leading to a stuck socket you will be able to close the connection properly. I also wanted to add a dialog to show what events/threads are currently running. I do not know of a way to terminate a thread as of yet. i still have to look into that.
Adding a verbose option to the debugging with the ability to specify what module/plugin you want to add it to.
Enhanced Device Events. this will include a payload of a device object that you can ask for different device settings/values
A complete overhaul of the System plugin. The list below contains the actions for device types i have already done. if there is anything you want to see added let me know and i will see what i can do.
Now nothing is etched in stone. but these are some of the things that you could see in eg 0.6
So if you are one of the people that are running the beta version and have discovered a problem. Then please share it with us so we can get it right before the full release. There is an infinate number of devices and setups so we can't test everything. Even tho we sure do try. So you beta testers are our front line to getting things resolved.
On another note.. We have Set the groundwork for EG 0.6 and this includes things like
This will be the biggest change you will see. I have been working on this for a couple of months now. But i have managed to code in a way to have each event that comes in to be run in it's own thread. so no more of having to wait for one macro to finish running before another can run. Now the real trick to this was how to make it backwards compatible. I have gotten a rough draft done up. The next trick was how to handle the logging aspects of it. and I came up with a nifty solution. and that was to make the main log only contain events and if you double click an event it will drop down to another log that shows everything that has taken place for that event. But this is going to add yet another feature (this can be enabled or disabled) But you will have the ability to access something like payload data for an event that has fired after other events have been run. this is nice for things like device states. or checking the last time an event was triggered. and you will no longer have to worry about running a polling loop in a python script WooHoo! all the threads that are created will be daemon threads. what this means is that if you close EG the threads will get terminated as well. I still have a couple of things i need to address with it like sending a notification that EG is closing. so that if a polling loop is for a network socket instead of just terminating and possibly leading to a stuck socket you will be able to close the connection properly. I also wanted to add a dialog to show what events/threads are currently running. I do not know of a way to terminate a thread as of yet. i still have to look into that.
Adding a verbose option to the debugging with the ability to specify what module/plugin you want to add it to.
Enhanced Device Events. this will include a payload of a device object that you can ask for different device settings/values
A complete overhaul of the System plugin. The list below contains the actions for device types i have already done. if there is anything you want to see added let me know and i will see what i can do.
Code: Select all
HDD/RemovableDrive/NetworkDrive:
Free drive space.
Total capacity
Type of file system
Starting chkDsk
Scheduling chkdsk at next reboot
Optical Drive:
Media type
Media size
Transfer rate
Portable Battery (laptop battery)\UPS:
Recharge time
Status
Estimated run time
Estimated charge remaining
Monitor:
Screen Size
Network Card:
Enable
Disable
Status
Connection speed
Video Card:
Video mode
Min refresh rate
Max refresh rate
Current refresh rate
Current resolution
