From: brett l. <wak...@gm...> - 2009-12-20 22:24:17
|
Adding the ability to play a whole new game (1856) was a a significant amount of work that really couldn't be pursued incrementally. Unfortunately, save file compatibility is something that occasionally will need to be broken. We don't like doing it, but this time around, it was unavoidable. Now that there are more people actively playing and testing, we're finding more bugs. Some are new, and some have probably been lurking around a while without being found. Overall, this is a step in the right direction. ---Brett. On Sun, Dec 20, 2009 at 2:06 PM, Jim Black <jim...@ya...> wrote: > >> Hard to say what the best time for a new bugfix release is. > > Some motherhood and apple pie here- > > With all the good development going on in Rails- naturally enough, but unfortunately- there's also enough associated bugs/issues that crop up constantly, that I hope you can move toward "faster and smaller" releases, in an agile style. > > It seems like 1.1 ended up being a bit of a 'waterfall' style release. That still puts artificial pressure on the developers and players to upgrade 'more stuff'- just, more desperately. > > More frequent 'minor/stable' releases/bugfixes/updates would be welcome, particularly if more could be done to help with release-to-release compatibility. (Eg, right now I can't upgrade my 1.0.6 games to 1.1, and can't load my 1.1 games in 1.0.6, etc- that's awkward and it would be a good area to improve iteratively, where pragmatic.) > > best, > - jim > > > On Dec 20, 2009, at 1:59 PM, Erik Vos wrote: > >> Actually, I just found the problem with UpgradesPanel: >> replacing repaint() by revalidate() did the job. >> Swing isn't so easy on certain aspects... >> >> Hard to say what the best time for a new bugfix release is. >> At one hand, we have this incompatibility with tile #4 >> (which will show up rotated when an old save file is >> loaded into the new version), and the danger of any more >> lurking (or newly introduced) bugs, on the other hand >> the OR-start bug just fixed is serious enough for a >> new release. >> >> Perhaps we should just go for it. >> >> Erik. >> >>> -----Original Message----- >>> From: brett lentz [mailto:wak...@gm...] >>> Sent: Sunday 20 December 2009 21:35 >>> To: Development list for Rails: an 18xx game >>> Subject: Re: [Rails-devel] 1856 in Rails 1.1.0 -- error >>> starting 1856 game >>> >>> Ok. Do you want to spend some time on the upgrades panel >>> before a new release? >>> >>> ---Brett. >>> >>> On Sun, Dec 20, 2009 at 7:50 AM, Erik Vos <eri...@xs...> wrote: >>>> I couldn't reproduce this particular error because of lack of info >>>> (I would need a saved file from a point shortly before the error, >>>> or a copy of the game report so that I can replay). >>>> >>>> But I'm pretty sure that behind this error is the serious bug >>>> that I found when playing some games. >>>> That bug inhibits all normal starts of the first >>>> (or perhaps any) OR in solitaire/hotseat play. >>>> For some unclear reason it didn't occur after loading from >>> a saved file. >>>> >>>> Anyway, I think it's fixed now, but some more testing is needed. >>>> >>>>>> Brett, this problem is serious enough that we'll need to >>>> prepare a new release pretty soon. >>>> >>>> I have also fixed a few other minor things. >>>> >>>> One bug remains a mystery: the disappearance of the upgrade tiles >>>> on selecting a different tile than the initially laid one. >>>> That upgrades panel needs a hard look. >>>> >>>> Erik. >>>> >>>> >>>>> -----Original Message----- >>>>> From: Aliza Panitz [mailto:ali...@gm...] >>>>> Sent: Sunday 20 December 2009 09:18 >>>>> To: Development list for Rails: an 18xx game >>>>> Subject: Re: [Rails-devel] 1856 in Rails 1.1.0 -- error >>>>> starting 1856 game >>>>> >>>>> 5p 1856 with me and 4 of my imaginary friends. Player D got no >>>>> privates, and floated a company at 75. After buying 4 shares, when >>>>> they are trying to pass with $0 in the first stock round, >>> , I get this >>>>> error: >>>>> >>>>> Exception in thread "AWT-EventQueue-0" >>> java.lang.NullPointerException >>>>> at >>> rails.game.OperatingRound.getStep(OperatingRound.java:1901) >>>>> at >>> rails.game.OperatingRound.nextStep(OperatingRound.java:944) >>>>> at rails.game.OperatingRound.done(OperatingRound.java:1202) >>>>> at >>> rails.game.OperatingRound.process(OperatingRound.java:261) >>>>> at rails.game.GameManager.process(GameManager.java:704) >>>>> at >>>>> >>> rails.ui.swing.GameUIManager.processOnServer(GameUIManager.java:133) >>>>> at >>> rails.ui.swing.StatusWindow.process(StatusWindow.java:533) >>>>> at >>>>> rails.ui.swing.StatusWindow.actionPerformed(StatusWindow.java:493) >>>>> at >>>>> javax.swing.AbstractButton.fireActionPerformed(Unknown Source) >>>>> at >>>>> javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) >>>>> at >>>>> javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) >>>>> at >>> javax.swing.DefaultButtonModel.setPressed(Unknown Source) >>>>> at >>>>> >>> javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Sour >>>>> ce) >>>>> at java.awt.Component.processMouseEvent(Unknown Source) >>>>> at javax.swing.JComponent.processMouseEvent(Unknown Source) >>>>> at java.awt.Component.processEvent(Unknown Source) >>>>> at java.awt.Container.processEvent(Unknown Source) >>>>> at java.awt.Component.dispatchEventImpl(Unknown Source) >>>>> at java.awt.Container.dispatchEventImpl(Unknown Source) >>>>> at java.awt.Component.dispatchEvent(Unknown Source) >>>>> at >>>>> java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) >>>>> at >>>>> java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) >>>>> at >>>>> java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) >>>>> at java.awt.Container.dispatchEventImpl(Unknown Source) >>>>> at java.awt.Window.dispatchEventImpl(Unknown Source) >>>>> at java.awt.Component.dispatchEvent(Unknown Source) >>>>> at java.awt.EventQueue.dispatchEvent(Unknown Source) >>>>> at >>>>> java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) >>>>> at >>>>> java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) >>>>> at >>>>> java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) >>>>> at java.awt.EventDispatchThread.pumpEvents(Unknown Source) >>>>> at java.awt.EventDispatchThread.pumpEvents(Unknown Source) >>>>> at java.awt.EventDispatchThread.run(Unknown Source) >>>>> >>>>> Clues? >>>>> >>>>> a: ship, tunnel, no shares, $120 >>>>> b: W&SR, GW 3@70, $70 >>>>> c: Flos, Canada, CPR 3@65, $45 >>>>> d: no privates, 4 GT@75, $0 >>>>> e: Bridge, 3 LPS@65, $20 >>>>> >>>>> d had priority in the stock round. >>>>> >>>>> -------------------------------------------------------------- >>>>> ---------------- >>>>> This SF.Net email is sponsored by the Verizon Developer Community >>>>> Take advantage of Verizon's best-in-class app development support >>>>> A streamlined, 14 day to market process makes app >>>>> distribution fast and easy >>>>> Join now and get one step closer to millions of Verizon customers >>>>> http://p.sf.net/sfu/verizon-dev2dev >>>>> _______________________________________________ >>>>> Rails-devel mailing list >>>>> Rai...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/rails-devel >>>> >>>> >>>> >>> -------------------------------------------------------------- >>> ---------------- >>>> This SF.Net email is sponsored by the Verizon Developer Community >>>> Take advantage of Verizon's best-in-class app development support >>>> A streamlined, 14 day to market process makes app >>> distribution fast and easy >>>> Join now and get one step closer to millions of Verizon customers >>>> http://p.sf.net/sfu/verizon-dev2dev >>>> _______________________________________________ >>>> Rails-devel mailing list >>>> Rai...@li... >>>> https://lists.sourceforge.net/lists/listinfo/rails-devel >>>> >>> >>> -------------------------------------------------------------- >>> ---------------- >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app >>> distribution fast and easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> Rails-devel mailing list >>> Rai...@li... >>> https://lists.sourceforge.net/lists/listinfo/rails-devel >>> >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Rails-devel mailing list >> Rai...@li... >> https://lists.sourceforge.net/lists/listinfo/rails-devel > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel > |