comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Non-sequential error
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Non-sequential error [message #18684] Thu, 03 February 2000 00:00 Go to next message
Steven Chetelat (CS) is currently offline  Steven Chetelat (CS)
Messages: 11
Registered: February 2000
Junior Member
I'm designing a program which calls another program I've written, and I'm
having a bit of a problem. The section I'm having problems with is:
str='mypro,'+thisim+','+newim
b=execute(str)
imarr(newint).occupied = 1
expr = 'im=smallsiz('+newim+',windowsizex,windowsizey)
res=execute(expr)

My problem is that mypro (a program which allows modification of newim
using widgets) begins execution, but then the following statements
execute, so the modifications from mypro don't take effect until the
program has advanced well beyond where they're needed...I was wondering if
this is supposed to happen, of if it's some shortcut the compiler takes
because of the execute statement, or what? I've tried a similar set of
statements in a test program, calling mypro, but I don't seem to have the
problem when I'm looking for it...any ideas?

K-Bye, STEVE!
(chetelat@csee.usf.edu)
Re: Non-sequential error [message #18813 is a reply to message #18684] Fri, 04 February 2000 00:00 Go to previous message
John-David T. Smith is currently offline  John-David T. Smith
Messages: 384
Registered: January 2000
Senior Member
William Thompson wrote:
>
> "Steven Chetelat (CS)" <chetelat@csee.usf.edu> writes:
>
>> I'm designing a program which calls another program I've written, and I'm
>> having a bit of a problem. The section I'm having problems with is:
>> str='mypro,'+thisim+','+newim
>> b=execute(str)
>> imarr(newint).occupied = 1
>> expr = 'im=smallsiz('+newim+',windowsizex,windowsizey)
>> res=execute(expr)
>
>> My problem is that mypro (a program which allows modification of newim
>> using widgets) begins execution, but then the following statements
>> execute, so the modifications from mypro don't take effect until the
>> program has advanced well beyond where they're needed...I was wondering if
>> this is supposed to happen, of if it's some shortcut the compiler takes
>> because of the execute statement, or what? I've tried a similar set of
>> statements in a test program, calling mypro, but I don't seem to have the
>> problem when I'm looking for it...any ideas?
>
>> K-Bye, STEVE!
>> (chetelat@csee.usf.edu)
>
> You'll need to execute mypro as a modal widget.

Or a blocking widget via XManager, /BLOCK.

JD

--
J.D. Smith |*| WORK: (607) 255-5842
Cornell University Dept. of Astronomy |*| (607) 255-6263
304 Space Sciences Bldg. |*| FAX: (607) 255-5875
Ithaca, NY 14853 |*|
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Faster than this...
Next Topic: Path handling in different OSs??

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 15:50:10 PDT 2025

Total time taken to generate the page: 0.00535 seconds