4 Commits

Author	SHA1	Message	Date
diva	dee6ad7154	Putting the return back in AddCapsHandler upon attempt at adding CAPs twice. The return seems to have been commented in 8038, as an attempt at fixing multiple TP problems later identified to be deadlocks. CAPs should never be overwritten, or the viewer can get confused. Right now this method is erroneously being called twice because of legacy code. I'll fix that later, after further testing.	2009-02-01 20:36:10 +00:00
Justin Clarke Casey	8a24f61acd	* Change the currently misleading log message when capabilities are added twice, and provide some more information ... * No functional change * It strikes me that there may be caps problems if double registration is presented if cleanup failed for a previous agent (so a caps handler will remain in memory for that agent but with a different seed). This needs investigation	2009-01-22 17:51:47 +00:00
Sean Dague	9704196bbf	* Caught 2 dictionary exceptions that were unhandled ... From: Arthur Rodrigo S Valadares <arthursv@linux.vnet.ibm.com>	2009-01-22 13:59:54 +00:00
Justin Clarke Casey	37fa677548	* refactor: Extract caps related code from scene and put into a region module ... * No functional changes in this revision	2009-01-21 21:14:17 +00:00