|
From: Nick C. <ni...@sr...> - 2001-08-19 16:42:13
|
On Fri, Aug 17, 2001 at 03:27:26PM -0500, Skye Bender-deMoll wrote: > Nick, > don't worry about this until you are moved! > > but, since I know you are going to look at the repast controller > strip and threading stuff anyway... > > I was testing the KK layout stuff with the NetTester model, and > discoverd that the "step" button doesn't always disable the "reload > button". This is an easily fixed bug. If you click step first, the reload button is not disabled. Just missing a single line to disable the reload button. > When I click the reload button (expecting it to fire the event > after the long update layout has finished), it seems to dump the objects > before the display surface is done with them, resulting in the display > surface throwing a whole pile of exceptions (one for each agent), and > the reload not occuring... This, as you've pointed out, is the result of the threading structure. I'll take a look at it after I get to Baltimore. I've been aware of it for a while, but its never been a priority to fix it. > just thought you should know, or would this be a good project for Tom to > get familiar with repast's event structure? ;-) (lord knows, even I > don't want to get THAT cozy with it!) > > -skye > > _______________________________________________ > Repast-developer mailing list > Rep...@li... > http://lists.sourceforge.net/lists/listinfo/repast-developer -- -------------- Nick Collier Social Science Research Computing University of Chicago http://repast.sourceforge.net |