<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Tips on developing Eclipse plugins - I.</title>
	<link>http://www.dolejsky.com/2007/12/16/tips-on-developing-eclipse-plugins-i/</link>
	<description>Things good to know...</description>
	<pubDate>Fri, 04 Jul 2008 13:49:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Tips on developing Eclipse plugins - III. - Project Decorators - dolejsky.com</title>
		<link>http://www.dolejsky.com/2007/12/16/tips-on-developing-eclipse-plugins-i/#comment-117</link>
		<dc:creator>Tips on developing Eclipse plugins - III. - Project Decorators - dolejsky.com</dc:creator>
		<pubDate>Mon, 30 Nov 2009 00:00:00 +0000</pubDate>
		<guid>http://www.dolejsky.com/2007/12/16/tips-on-developing-eclipse-plugins-i/#comment-117</guid>
		<description>[...] Sometimes it is needed to force the refresh of the decorations (e.g. when they depend on some internal state which has changed). It can be achieved by firing fireLabelProviderChanged() event of the decorator (if it is enabled). This has to be done in UI thread (as described here). [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Sometimes it is needed to force the refresh of the decorations (e.g. when they depend on some internal state which has changed). It can be achieved by firing fireLabelProviderChanged() event of the decorator (if it is enabled). This has to be done in UI thread (as described here). [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
