unofficial fahmon updates

OK, so you may be wondering how/why I got this release out so quickly. Well the answer is, I've just finished my last lecture of the year, and wanted to relax before I start revising for finals and writing reports and essays.

So without further ado, here's what new (cringe):

• Fixed a bug that causes fahmon not to update the Work Unit Information panel properly. See here. Thanks to RipD for the heads up on this one.
• Added a system tray menu which display some useful info, and lets you show/hide the client and open the benchmarks and preferences windows
  
• Added an option to the per-client right-click menu, to allow you to open the containing folder. On the menu this is called "View Client Files". Thanks to Bruce for this suggestion.
  

This last option also introduces a change to the Preferences Dialog. A new "System" page has been added, the Browser configuration has been moved from the General page to Settings, and renamed to Web Browser. In addition, to support the "View Client Files" feature, another option has been added to the System Page: File Manager.

This comes in the form of a dropdown list containing common file manager selections for Windows and Linux, depending on host OS, and also a manual command box for you to either edit the default commands, or enter new ones.

Choosing an unavailable file manager, or incorrect/invalid command will fail silently.

Download (Windows): fahmon_2.1.5b.5.zip

Download (Linux): fahmon_2.1.5b.5.tbz2

The problem: If a client you are monitoring is processing a project that happens to be missing from psummary, the Work Unit Information Panel isn't cleared. If you monitor multiple clients, switching to this "broken" client will leave all the information from the previous client in view, except for the project number. This happens if you have auto update projects enabled. The reason for this breakage, is that fahmon assumes that once the project database is updated it will then contain the data you need, and won't bother clearing it, it just waits for the information to be overwritten. Unfortunately there is no fallback procedure for when the updated database is still missing the data.

The solution: Reset all the data before updating the project list. This way everything gets set to N/A, and if the project info doesn't exist, it doesn't get overwritten.

mainDialog.diff

--- a/mainDialog.cpp	2007-02-01 00:02:29.000000000 +0000
+++ b/mainDialog.cpp	2007-03-16 13:16:04.000000000 +0000
@@ -377,6 +377,16 @@
     // This project can be unknown, if the database is not up to date
     if(project == NULL)
     {
+
+        // Fallback to reset all info in case psummary doesn't contain the data we need
+        // Otherwise bad things happen like the data remaining from the last client viewed
+
+        mProjectId->SetLabel(wxT("N/A"));
+        mCoreName->SetLabel(wxT("N/A"));
+        mCredit->SetLabel(wxT("N/A"));
+        mPreferredDeadline->SetLabel(wxT("N/A"));
+        mFinalDeadline->SetLabel(wxT("N/A"));
+
         // Update the database, if the user wants to
         // This update is not forced, it will occur only if the elapsed time since the last one is high enough
         // This way, we ensure that we won't perform many multiple requests for the file, while it does not