client: don't show notices about not being able to do certain types o…

…f work

after a scheduler RPC.
These are shown at startup.
The only thing that may have changed is project prefs (e.g. no GPU)
and the user did that - we don't need to remind them that they did it.

client/cs_account.cpp

@@ -95,6 +95,7 @@ static void handle_no_rsc_pref(PROJECT* p, const char* name) {
 
 // parse an account_*.xml file, ignoring <venue> elements
 // (since we don't know the host venue yet)
+// Called at startup and after scheduler RPC
 //
 int PROJECT::parse_account(FILE* in) {
     char buf2[256];
@@ -195,6 +196,7 @@ int PROJECT::parse_account(FILE* in) {
 // and parsing that for resource share and prefs.
 // Call this only after client_state.xml has been read
 // (so that we know the host venue)
+// Called at startup and after scheduler RPC
 //
 int PROJECT::parse_account_file_venue() {
     char attr_buf[256], venue[256], path[MAXPATHLEN], buf2[256];

client/cs_scheduler.cpp

@@ -763,10 +763,11 @@ int CLIENT_STATE::handle_scheduler_reply(
         active_tasks.request_reread_prefs(project);
     }
 
-    // show notice if we can't possibly get work from this project.
-    // This must come after parsing project prefs
+    // notices here serve no purpose.
+    // The only thing that may have changed is project prefs,
+    // and there's no reason to tell the user what they just did.
     //
-    project->show_no_work_notice();
+    //project->show_no_work_notice();
 
     // if the scheduler reply includes a code-signing key,
     // accept it if we don't already have one from the project.