rails-devel

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

[Aliza P. <ali...@gm...>]

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.

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

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

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

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

[brett l. <wak...@gm...>]

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
>

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

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

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
> 

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

[brett l. <wak...@gm...>]

I agree.   Release early, release often. ;-)

I'll post 1.1.1 shortly.

---Brett.



On Sun, Dec 20, 2009 at 1:59 PM, Erik Vos <eri...@xs...> 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
>

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

[Jim B. <jim...@ya...>]

> 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

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

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

> 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.

Yes, it has lasted a bit too long. That was partly due to
my inactivity for quite a number of months, followed by
a flurry of updates when I pretty suddenly got quite some
spare time. That may well diminish in the coming months...

BTW I have asked Brett to investigate if it would be possible
to have two downloadable releases available, as so many other
projects have: a "latest stable release" and a "nightly build"
to give adventurous users a chance to see and test what is 
about to come. The latter doesn't really need to be nightly, 
but it should be regular and automatic. Not sure if this 
will turn out to be possible.
 
> 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.)

Compatibility is indeed a goal. I'm already for some time
adding special code for that purpose where applicable. 
But sometimes incompatibility is caused by fixing a bug 
that has caused old save file sequences to be invalid, 
and then it can't be avoided.

Erik.

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

[Aliza P. <ali...@gm...>]

A standalone convert-savefile tool might help support users while
protecting the program itself from issues.

Then again, I am not a Java programmer and can't help implement it.

Given how much work it's taken getting 1856 up and running even
partway, how much development is being put into making it easier to
extend Rails to new games?

 - Aliza

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

[Chris S. <chr...@gm...>]

I'm not sure I understand why someone can't simply run two copies of the
program - one for their older games and one for new games?

--
Chris

Please consider the environment before printing this e-mail.


On Sun, Dec 20, 2009 at 4:32 PM, Aliza Panitz <ali...@gm...>wrote:

> A standalone convert-savefile tool might help support users while
> protecting the program itself from issues.
>
> Then again, I am not a Java programmer and can't help implement it.
>
> Given how much work it's taken getting 1856 up and running even
> partway, how much development is being put into making it easier to
> extend Rails to new games?
>
>  - Aliza
>
>
> ------------------------------------------------------------------------------
> 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
>

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

[Aliza P. <ali...@gm...>]

It's really easy to accidentally open a game in the wrong version and trash it.

On Sun, Dec 20, 2009 at 5:24 PM, Chris Shaffer <chr...@gm...> wrote:
> I'm not sure I understand why someone can't simply run two copies of the
> program - one for their older games and one for new games?
>
> --
> Chris
>

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

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

> It's really easy to accidentally open a game in the wrong 
> version and trash it.
> 

I could have updated the built-in version number that prevents 
you from loading old save files into newer Rails versions. 
I didn't just because I completely overlooked it. 
And if I hadn't I might have skipped it equally well, 
for various reasons. In fact I'm now actively trying
to avoid the need to declare such version incompatibilities.

I believe that with 1.1.0, only some old save files 
don't work any longer (because these had invalid moves),
which (if I had thought about it) might have been another 
reason to avoid making the loading of old save files impossible.
Most of my own save files used for testing still work.

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

[Jim B. <jim...@ya...>]

I do switch versions w/ different games, but it's quite awkward, and error prone.  More problematic, it causes cascading interdependencies across players- where everyone has to upgrade in step, and run multiple different versions across their different games, etc.  

Surprisingly, in practice the combinatorials get out of hand really quickly- it seems to be causing a lot of problems across players and games, at present.




On Dec 20, 2009, at 5:24 PM, Chris Shaffer wrote:

> I'm not sure I understand why someone can't simply run two copies of the program - one for their older games and one for new games?
> 
> --
> Chris
> 
> Please consider the environment before printing this e-mail.
> 
> 
> On Sun, Dec 20, 2009 at 4:32 PM, Aliza Panitz <ali...@gm...> wrote:
> A standalone convert-savefile tool might help support users while
> protecting the program itself from issues.
> 
> Then again, I am not a Java programmer and can't help implement it.
> 
> Given how much work it's taken getting 1856 up and running even
> partway, how much development is being put into making it easier to
> extend Rails to new games?
> 
>  - Aliza
> 
> ------------------------------------------------------------------------------
> 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

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

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

See inserts below.
 


  _____  

From: Jim Black [mailto:jim...@ya...] 
Sent: Monday 21 December 2009 04:28
To: Development list for Rails: an 18xx game
Subject: Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game


I do switch versions w/ different games, but it's quite awkward, and error
prone.  More problematic, it causes cascading interdependencies across
players- where everyone has to upgrade in step, and run multiple different
versions across their different games, etc.   


Surprisingly, in practice the combinatorials get out of hand really quickly-
it seems to be causing a lot of problems across players and games, at
present.

Hopefully Rails will turn out to be more stable in the near future.
A lot has happened recently, and some behind-the-scenes structural 
changes have had more side-effects (i.e. caused bugs) than I had
expected. 
 
I think that all has about settled now, the GUI looks better in several
respects,
and once it's clear that there are no more critical bugs, I plan to return
to implementing new games (maybe also because 2 out of 2 voters in the 
18xx Yahoo group found that the most important new development to do :-).
 


Given how much work it's taken getting 1856 up and running even
partway, how much development is being put into making it easier to
extend Rails to new games?

 - Aliza


The current plan is first to look at the two now half-implemented games 1835
and 1870. 
Each one has quite some new aspects that will need fairly extensive
programming,
so I can't tell when anything gets finished.
 
I'm constantly trying to implement new features in a generic way, so that 
other games with the same feature might be easier to do, but it doesn't
always work out like that. In general it is impossible to predict how hard
implementing a new feature is. Sometimes it's a matter of hours, sometimes
days, weeks or months. 
 
1856 took almost a year, partly because the CGR formation with all its
details 
was very hard to get right in all possible permutations of circumstances.
Now that such a merger has been done, others may turn out to be easier to do
(such as the 1835 Prussian merger), but equally well, they may not.
 
Another example: private special properties have almost always been
difficult. 
By now, enough groundwork might have been done to make future ones easier
to do, but there is no guarantee. 
 
Last of all, the time I can (and want to) spend on this work fluctuates
heavily.
I also have a day job, a family, and several more hobbies....
 
Erik.

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

[Mark S. <mar...@gm...>]

Erik,

One of the items you mentioned is to prevent a new version from being able
to open an older (incompatible) saved game.

What might be very simple is to add an "<VERSION>1.1.1</VERSION>" tag to the
save game file (at the begining). If the tag is NOT present, display a
warning dialog "Save File does not appear to be a compatible version, Load
Anyway?" with a YES, and NO button. This would allow a player to try and
load it, but the player is warned.

Mark

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

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

Your proposal makes much sense. The only problem is that a version
difference does not always imply incompability. 
 
In fact two different version numbers are already included in
saved files: the public one, and an internally hardcoded one.
The latter one in fact does the incompatibility check, 
but right now it just aborts loading. 
You may see it at work when loading VERY old saved files. 
 
I like your proposal to let the user decide instead.
But that will not help out with the current version.
 
Erik.


  _____  

From: Mark Smith [mailto:mar...@gm...] 
Sent: Monday 21 December 2009 18:47
To: Development list for Rails: an 18xx game
Subject: Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game


Erik,

One of the items you mentioned is to prevent a new version from being able
to open an older (incompatible) saved game.

What might be very simple is to add an "<VERSION>1.1.1</VERSION>" tag to the
save game file (at the begining). If the tag is NOT present, display a
warning dialog "Save File does not appear to be a compatible version, Load
Anyway?" with a YES, and NO button. This would allow a player to try and
load it, but the player is warned.

Mark

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

[Jim B. <jim...@ya...>]

> The only problem is that a version difference does not always imply incompability.

It does, more than Rails seems to realize.  

Sometimes a newer version will successfully load an older version's save, but present a different resulting state/game- different $$ balance, different stock prices, etc.  The Rails users I'm playing with all are having problems with this issue, and the resulting difficulty of running / maintaining multiple versions in parallel across different games, etc.  

> I plan to return to implementing new games (maybe also because 2 out of 2 
> voters in the 18xx Yahoo group found that the most important new development to do :-).

I'm not meaning to be negative, I'm a big Rails fan- but, I do think that stability, and more work with version-to-version compatibility, is a higher priority than new game support, features for online play, etc.  That's just one vote (mine)- but, by my math, that means you have registered at least 3 votes/opinions- not just 2.  ;)
 
 - jim

On Dec 21, 2009, at 10:13 AM, Erik Vos wrote:

> Your proposal makes much sense. The only problem is that a version
> difference does not always imply incompability.
>  
> In fact two different version numbers are already included in
> saved files: the public one, and an internally hardcoded one.
> The latter one in fact does the incompatibility check,
> but right now it just aborts loading.
> You may see it at work when loading VERY old saved files.
>  
> I like your proposal to let the user decide instead.
> But that will not help out with the current version.
>  
> Erik.
> 
> From: Mark Smith [mailto:mar...@gm...] 
> Sent: Monday 21 December 2009 18:47
> To: Development list for Rails: an 18xx game
> Subject: Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game
> 
> Erik,
> 
> One of the items you mentioned is to prevent a new version from being able to open an older (incompatible) saved game.
> 
> What might be very simple is to add an "<VERSION>1.1.1</VERSION>" tag to the save game file (at the begining). If the tag is NOT present, display a warning dialog "Save File does not appear to be a compatible version, Load Anyway?" with a YES, and NO button. This would allow a player to try and load it, but the player is warned.
> 
> Mark
> ------------------------------------------------------------------------------
> 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

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

[brett l. <wak...@gm...>]

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
>

Re: [Rails-devel] 1856 in Rails 1.1.0 -- error starting 1856 game

[Jim B. <jim...@ya...>]

Right, totally understandable- it would just would be nice to have some incremental releases for a while, if possible.  %->


On Dec 20, 2009, at 2:23 PM, brett lentz wrote:

> 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
>> 
> 
> ------------------------------------------------------------------------------
> 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