Skip to main content
summaryrefslogtreecommitdiffstats
blob: 91e73698daa59db9a3f459f44b68d16a49fcfe35 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
<article link="article.html" show="false">
	<title>How to Correctly and Uniformly Use Progress Monitors</title>
	<date>January 3, 2006</date>
	<category>platform</category>
	<category>general</category>
	<author>
		<name>
			<![CDATA[Kenneth &Ouml;lwing]]>
		</name>
		<company>BEA JRPG</company>
	</author>
	<description>
		Handling a progress monitor instance is deceptively simple. It
		seems to be straightforward but it is easy to make a mistake
		when using them. And, depending on numerous factors such as the
		underlying implementation, how it is displayed, the result can
		range from completely ok, mildly confusing or outright
		silliness. In this article we lay down a few ground rules that
		will help anyone use progress monitors in a way that will work
		with the explicit and implicit contract of IProgressMonitor.
		Also, understanding the usage side makes it easier to understand
		how to implement a monitor.
	</description>
</article>

Back to the top