eq.gimasoft.com

I'll have to look into this, but it probably won't be this week when I get to look into it. My guess is that it doesn't like the fact that the download is unsigned.

In the log section at the bottom of GINA, How difficult would it be to make it so in a new column it would show the line of text that triggered the audio trigger. I"ll add this in the next release I do. On a side note, how would you write a regular expression to report that? I tried to think of how...

I'm working on a control to replace the library section, so I'll keep this in mind.

The change log for version updates can be found here on the main web site.

#5 (copy ability on the match log) is now supported in version 1.0.11.9. In the displayed match log, you can Copy selected entries (Ctrl-C or right-click -> Copy) or "Copy as HTML" for selected entries (right-click -> Copy as HTML). In addition, you can have all matches written to a tab-delimited lo...

Validation is now in. If you try to export a trigger that GTT does not support, you will now get an error message. There are a couple scenarios where GINA will try to transform the trigger to conform to one that GTT can support: If the {C} tag is used in the Search Text and the {S} has not been used...

This is now an option on the Settings window in 1.0.11.9. By default it is disabled, so you will need to enable it.

I will add this to my list as an optional setting. GINA doesn't really fit the standards & practices for making it a notification icon-based app in the system tray, but I've had this request a couple times now.

The changelog on the main web site can be found here: http://eq.gimasoft.com/gina/ChangeLog.aspx I usually try to limit the patches to 1 a day, but I had a couple of important bug fixes that I wanted to push right away today. Sorry about the duplicate names -- it was happening in the Check For Updat...

I was able to recreate the issue on an SSD drive. The issue is corrected in the latest version, 1.0.11.7. Thanks for reporting this!