tag:blogger.com,1999:blog-4451657389087868432.post7684809790827448509..comments2023-05-29T02:10:01.374-06:00Comments on sworldwatch: progress counters and dialogsAlfred Sawatzkyhttp://www.blogger.com/profile/15845723068853240174noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-4451657389087868432.post-21986302083102503682007-06-25T10:18:00.000-06:002007-06-25T10:18:00.000-06:00Alfred,Interesting code and very useful for the us...Alfred,<BR/>Interesting code and very useful for the users who are trigger-happy. I tried something like this the other day with a plugin that was running a trace to capture the downstream kva load.<BR/>So to do this, before I start looping over the circuits I'm about to trace, I call _self.install_progress_indicator() passing in the name and engine. The problem however is that when we're tracing out of say 3 circuits we don't know if one of the circuits is short and the other long. In situations like this how can a progress_indicator be used effectively to indicate the progress when the trace time will vary from one circuit to the next? The progress_indicator needs to know the increments and the max_count in order to show the progress. In this situation all I could indicate to the user was that one circuit was traced and then the next one, and finally the third. Not very effective.<BR/><BR/>I'm not sure that this was my problem but for the 'engine' parameter for the indicator I was passing in the plugin itself rather than the trace engine that I had stored in the plugin's slot. Could this have been the issue?<BR/><BR/>btw, love the Blog...Thanks.<BR/><BR/>RobRobert Lilleyhttps://www.blogger.com/profile/04725082459816087945noreply@blogger.com