| Re: print statements not working with dicom series uids? [message #66477] |
Wed, 20 May 2009 17:15  |
justin.mikell
Messages: 5
Registered: May 2009
|
Junior Member |
|
|
On May 20, 7:10 am, "Jean H." <jghas...@DELTHIS.ucalgary.ANDTHIS.ca>
wrote:
> justin.mik...@gmail.com wrote:
>> I use IDL 7.0 on windows XP.
>
>> When I execute the program, IDL chooses not to print certain
>> statements.
>> All the suspect print statements are trying to print a dicom series
>> uid string.
>
>> However, when I place a breakpoint and then step through the statement
>> it prints to screen.
>
>> -Justin
>
> Hi Justin,
>
> I have witnessed, today, that some statements are "partly printed"...
> If I look at the console output (winXP, IDL 7.0.8) the expected line is
> not there... but moving up and down in the console makes the line
> automagically appear! Strange.
>
> Jean
I am unable to have them appear by moving the console position. They
do appear when I print to an actual file instead of the console.
|
|
|
|
|
|
| Re: print statements not working with dicom series uids? [message #66565 is a reply to message #66477] |
Thu, 21 May 2009 09:49  |
bill.dman
Messages: 17
Registered: June 2007
|
Junior Member |
|
|
On May 20, 8:15 pm, justin.mik...@gmail.com wrote:
> On May 20, 7:10 am, "Jean H." <jghas...@DELTHIS.ucalgary.ANDTHIS.ca>
> wrote:
>
>
>
>> justin.mik...@gmail.com wrote:
>>> I use IDL 7.0 on windows XP.
>
>>> When I execute the program, IDL chooses not to print certain
>>> statements.
>>> All the suspect print statements are trying to print a dicom series
>>> uid string.
>
>>> However, when I place a breakpoint and then step through the statement
>>> it prints to screen.
>
>>> -Justin
>
>> Hi Justin,
>
>> I have witnessed, today, that some statements are "partly printed"...
>> If I look at the console output (winXP, IDL 7.0.8) the expected line is
>> not there... but moving up and down in the console makes the line
>> automagically appear! Strange.
>
>> Jean
>
> I am unable to have them appear by moving the console position. They
> do appear when I print to an actual file instead of the console.
I remember experiencing something like this when using idlffdicom, and
tracked it down to
there being at least one null character at the end of the UID. See if
this helps:
function str_remove_trailing_null, string_in
compile_opt strictarr
s1 = strmid(string_in, 0, strlen(string_in)-1)
return, s1 eq string_in ? s1 : string_in
end
uid = strtrim(str_remove_trailing_null(*dcmvalptr[0]),2)
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
