| Re: Writing to the IDLde [message #52541] |
Wed, 14 February 2007 01:13  |
Ben Panter
Messages: 102
Registered: July 2003
|
Senior Member |
|
|
R.G. Stockwell wrote:
> 2) create a new procedure like "printstatus" that does what you want,
> and then globally search and replace all your print functions.
As I understand it that's the point of the query - such a procedure
appears to be impossible in the IDLDE. I have lots of processes that
include long iterative calculations, and having a %age done line that
doesn't destroy the whole log would be great - in fact, even being able
to run successive print statements on the same line rather than a new
line would help.
At the moment I just have a test that prints i if i mod X is 0, where i
is the iteration number and X is the frequency at which I want to know
what it's up to. Far from ideal though...
Ben
--
Ben Panter, Edinburgh, UK.
Email false, http://www.benpanter.co.uk
or you could try ben at ^^^^^^^^^^^^^^^
|
|
|
|
|
|
| Re: Writing to the IDLde [message #52683 is a reply to message #52541] |
Wed, 14 February 2007 08:21  |
news.qwest.net
Messages: 137
Registered: September 2005
|
Senior Member |
|
|
"Ben Panter" <me@privacy.net> wrote in message
news:53g26cF1so8jfU1@mid.individual.net...
> R.G. Stockwell wrote:
>
>> 2) create a new procedure like "printstatus" that does what you want,
>> and then globally search and replace all your print functions.
>
> As I understand it that's the point of the query - such a procedure
> appears to be impossible in the IDLDE. I have lots of processes that
> include long iterative calculations, and having a %age done line that
> doesn't destroy the whole log would be great - in fact, even being able to
> run successive print statements on the same line rather than a new line
> would help.
>
> At the moment I just have a test that prints i if i mod X is 0, where i is
> the iteration number and X is the frequency at which I want to know what
> it's up to. Far from ideal though...
>
> Ben
Right, I agree that you cannot do it to the IDE window.
What I meant was to have a function that did some
appropriate solution, such as a "progress" widget like
Dave Fanning's. Or one could make a graphics window
and xyout the message.
One can erase the window then make the new message,
or rewrite the old message in the background color (thereby
'erasing' it) and write the new message in the foreground color.
There are a lot of possibilites, and it should be very straightforward
to implement. If not, perhaps the OP can elaborate on what the problem is.
Cheers,
bob
|
|
|
|
| Re: Writing to the IDLde [message #52685 is a reply to message #52541] |
Wed, 14 February 2007 06:27 |
Kenneth Bowman
Messages: 86
Registered: November 2006
|
Member |
|
|
In article <53g26cF1so8jfU1@mid.individual.net>, Ben Panter <me@privacy.net>
wrote:
> R.G. Stockwell wrote:
>
>> 2) create a new procedure like "printstatus" that does what you want,
>> and then globally search and replace all your print functions.
>
> As I understand it that's the point of the query - such a procedure
> appears to be impossible in the IDLDE. I have lots of processes that
> include long iterative calculations, and having a %age done line that
> doesn't destroy the whole log would be great - in fact, even being able
> to run successive print statements on the same line rather than a new
> line would help.
>
> At the moment I just have a test that prints i if i mod X is 0, where i
> is the iteration number and X is the frequency at which I want to know
> what it's up to. Far from ideal though...
>
> Ben
You could try David's showprogress widget
http://www.dfanning.com/widget_tips/show_progress.html
Ken Bowman
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
