After looking at this is looks very similar to the WPF delegate. Thanks for the direction on this, I think I now have the answers I need, and this will also allow me to better separate my design from the data backing it.
Thanks for all the answers! -- Ryan Moore On Thu, Mar 24, 2011 at 9:32 AM, Greg Brown <[email protected]> wrote: > If you are calling it from a background thread, make sure you are using > ApplicationContext.queueCallback() to call into the UI thread. Otherwise, > you may see unpredictable behavior such as the flickering you mentioned. > > On Mar 24, 2011, at 11:21 AM, Ryan Moore wrote: > > I saw this flicker on Ubuntu (I have replaced the default jdk with the > sun/oracle version not the open jdk) last night, and when I say flicker I > mean there was a slight image leftover as I would swap between what elements > that where selected, it quickly went away however. I want to say that I am > calling it from the background thread, or at least from my main thread of > execution for the application. I have set up an event and data propagation > system within my app to update the data bound to the tableView, this is > where I am calling the setSelectedIndex(). > > -- > Ryan Moore > > On Thu, Mar 24, 2011 at 7:04 AM, Greg Brown <[email protected]> wrote: > >> > I don't have the source in front of me, but TableView#setSelectedIndex() >> most likely results in a call to scrollAreaToVisible() anyway. >> >> That is correct. There should not be any flicker, however. Can you provide >> any more detail about this issue? What OS are you using? Are you by any >> chance calling setSelectedIndex() from a background thread? >> >> >> > >
