Klaus, do you still have this problem. There may indeed be a race condition associated with the sequence of calling setVisible() and the dialog initialization code. This will be addressed in the next release.
On Thursday, May 9, 2013 11:24:36 AM UTC-4, Klaus wrote: > > Wow, now it gets even more interesting: > if I set a breakpoint at line 38 of MainFrameDialog (at setVisible(true)). > The execution stops there, I inspect the strategyTableModel, the table > contains the strategies. > I step through the "setVisible" - everything is fine. > If I remove this break point and just run it in debugging mode (in order > to keep everything the same), > it fails: I get an empty table shown! > > Based on this I just put there a second setVisible(true), now it seems to > work - some form of race condition? > > Klaus > > > Am Donnerstag, 9. Mai 2013 15:08:28 UTC+2 schrieb Klaus: >> >> I usually have a private version of JBT and a copy of the latest status >> of the JBT version in the mercurial repository. >> >> Now I updated the second the latest JBT after some time and found that I >> can start it, but it does not show any strategies >> although two strategies are shown in the source. >> >> Is this a general phenomenon or is it particular to my installation. >> Anyone an idea what the problem might be ? >> >> Klaus >> >> -- You received this message because you are subscribed to the Google Groups "JBookTrader" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/jbooktrader. For more options, visit https://groups.google.com/groups/opt_out.
