From: Erik V. <eri...@hc...> - 2006-01-14 20:59:17
|
This bug should have been fixed now. > I suspect that this section of code was written before you > implemented multiple ORs between each SR. So, I think we'd > have this bug regardless of the unified JFrame or not. (I > think I've encountered it before.) You're absolutely right. > >I also had a compilation error that GUIHex and HexMap could no > >longer access StatusWindow.orWindow, because that field seems > >to have been made private. I now use a method to get this object > >(the proper way!). > > > > Huh. I'd swear I committed changes with a getter method for > orWindow. Apparently I was wrong. To be honest, this is not the first time that I have to correct a compiliation error after an update. It is always a small thing, so I tend to keep silent about it. But it looks as if your synchronisation is not always complete. Erik. |