|
| Re: Removing a Model Element causes Invalid thread access [message #533493 is a reply to message #533186] |
Fri, 14 May 2010 09:15   |
Vijay Raj
Messages: 608
Registered: July 2009 |
Senior Member |
|
|
replace your refreshChildren method code like this
refreshChildren()
{
Display.getDefault().syncExec(new runnable()
{
//Method code
}
}
This is not required usually because the delete happens from ui only, but in your case the java file file has been deleted and that notification is non UI thread.
---------------------
why, mr. Anderson, why, why do you persist?
Because I Choose To.
Regards,
Vijay
|
|
|
| Re: Removing a Model Element causes Invalid thread access [message #533794 is a reply to message #533493] |
Mon, 17 May 2010 06:33 |
 Chris 
Messages: 44
Registered: April 2010 |
Member |
|
|
Hi,
I wanted to thank you, your tip set me on the right track for the final solution of the problem.
With a bit of modification, your tip worked just fine. I did not override the refreshChildren method in my EditPart, so I wrapped its only occurence in propertyChange. That helped a bit. I still got the exception, but the MVC got all updated correctly and the editor would no longer freeze.
The next step was a good long look at the stack trace. Looking at it, I decided, the best place to catch the exception would be in the firePropertyChange method. So I created a nested class FirePropertyChangeRunnable implementing the Runnable interface and accepting the three arguments of firePropertyChange in the constructor.
Now, any time my model would call firePropertyChange , it calls
Display.getDefault().syncExec(new FirePropertyChangeRunnable(CHILD_REMOVED_PROPERTY, null, child));
instead.
So thanks again, you made my day 
Regards,
Chris
|
|
|
Powered by
FUDForum. Page generated in 0.32034 seconds
] 
Search
Help
Register
Login
Home
