🚀 go-pugleaf

Tom Giammo wrote:
> Paul:
> 
> Thanks for responding.
> 
> Your approach is ingenious and no doubt would work.  I had begun to explore 
> along those lines myself, but couldn't keep straight in my mind which 
> variables would be visible to the components within the top-level frame.  I 
> ultimately gave up on the basis that something so simple as accessing a 
> sibling component of the same top-level couldn't possibly be so complex.  I 
> also found the necessity of modifying the JBuilder generated code so 
> significantly a bit distasteful.
> 
> Upon much reflection <pun intended>, I think that I've come up with a 
> simpler way that is less disruptive of the JBuilder code.  I was on the 
> right track when I tried to find the top-level frame containing my component 
> using the component's "getParent()" method.  In this regard, I think that 
> your comment on this approach ("Will not work, you are attempting to bypass 
> encapsulation rules") is not correct.  

Could be. I was under the assumption that you were using a class called 
Main that contained a reference to the class HexGame, which was not part 
of the Main class itself, therefore, you were attempting to access it 
out of scope. But if this was incorrect, then of course my assumption 
would be incorrect.

Of course without possessing the actual code, all one can do is guess :)