Re: [Rails-devel] 1.0.7-rc1 is up

[Erik V. <eri...@hc...>]

Jim,

That was a stupid oversight in the code. Sorry for that. I'm afraid I have
never tested this situation.

It's now fixed in the code base, and the error has disappeared.
If you can't use that, perhaps Brett would be willing to publish a new
pre-release?

Best regards,
Erik. 

> -----Original Message-----
> From: Jim Black [mailto:jim...@ya...] 
> Sent: Tuesday 10 November 2009 20:50
> To: Development list for Rails: an 18xx game
> Subject: Re: [Rails-devel] 1.0.7-rc1 is up
> 
> 
> I'm seeing a bug/problem with rails in a current 1830 game w. 1.0.6,  
> it appears there's some fatal problems with adjusting stocks 
> that are  
> already at 'rock bottom'.
> 
> In this specific case (.rails file is attached), the NYNH is 
> at one of  
> the lhs corners of the stock chart (at $10), and Rails is crashing  
> when the NYNH runs.
> 
> I see errors in the log --
>    Cmdline configfile setting = null
>    Configuration file = my.properties
>    Exception in thread "AWT-EventQueue-0" 
> java.lang.NullPointerException
> 	at rails.game.StockMarket.moveLeftOrDown(StockMarket.java:278)
> 	at rails.game.StockMarket.withhold(StockMarket.java:196)
> 	at rails.game.PublicCompany.withhold(PublicCompany.java:1169)
> 	at rails.game.OperatingRound.nextStep(OperatingRound.java:809)
> 	at rails.game.OperatingRound.nextStep(OperatingRound.java:770)
> 	at rails.game.OperatingRound.skip(OperatingRound.java:1008)
> 	at rails.game.OperatingRound.process(OperatingRound.java:219)
> 	at rails.game.GameManager.process(GameManager.java:530)
> 	at 
> rails.ui.swing.GameUIManager.processOnServer(GameUIManager.java:121)
> 	at rails.ui.swing.ORWindow.process(ORWindow.java:127)
> 	at 
> rails.ui.swing.ORUIManager.cancelUpgrade(ORUIManager.java:1024)
> 	at 
> rails.ui.swing.UpgradesPanel.actionPerformed(UpgradesPanel.java:257)
> 	at 
> javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java: 
> 2028)
> 
> Which appears to confirm that it's moving the stock price that's  
> triggering this problem.
> 
> I tried to upgrade to 1.0.7 pre-release, to see if that fixed this-  
> but no luck.  (same problem, in fact I think that log message 
> I quoted  
> above was actually from my test with 1.0.7.)
> 
> I can file the defect/incident- but, any ideas on how I might work  
> around this and proceed with our game?  (Not sure we'll be able to  
> play it out.)
> 
> thanks in advance, for any tips,
>   -  jim
> 
>