[ https://issues.jboss.org/browse/JBIDE-7852?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-7852 at 12/9/10 12:59 PM: ------------------------------------------------------------------- resolved this together with the changes to JBIDE-7848. I now separated the 2 usecases: - active data fetching: a view gets the data it wants to display - passive data fetching: a view gets notified if its data was changed The former implementation did treat both cases in the same way. So If the CloudView hat its tree filled with images and the ImageView then fetched data, the CloudView was notified of new data and refreshed its images. The CloudView therefore collapsed the images branch and lost its selection. I solved this by separating those 2 usecases. Views are now only notified if their data changes. They now get their data and block until the data is available and returned to them. Its in their own responsability to use jobs/threads to fetch the data and update their widgets accordingly. Committed to TRUNK (CR1) was (Author: adietish): resolved with JBIDE-7848. I now separated the 2 usecases: - active data fetching: a view gets the data it wants to display - passive data fetching: a view gets notified if its data was changed The former implementation did treat both cases in the same way. So If the CloudView hat its tree filled with images and the ImageView then fetched data, the CloudView was notified of new data and refreshed its images. The CloudView therefore collapsed the images branch and lost its selection. I solved this by separating those 2 usecases. Views are now only notified if their data changes. They now get their data and block until the data is available and returned to them. Its in their own responsability to use jobs/threads to fetch the data and update their widgets accordingly. Committed to TRUNK (CR1) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira