Replace the Sequencer with a Loop to do what you want if you program
in the VPE. Otherwise, edit MRI_2.net and before the play; command,
issue:
palindrome on;
loop on;
play;
I now see that there must be a bug there somewhere. If I drop into
script mode and do the following:
dx> include "MRI
Update of /src/master/dx
In directory opendx.watson.ibm.com:/tmp/cvs-serv11900
Modified Files:
ChangeLog
Log Message:
Update to be able to build loadable modules correctly on AIX 4.2 and
higher. This eliminates compatibility with older systems but 4.1 is
at least 7 years old (users should
Update of /src/master/dx/src/exec/dpexec
In directory opendx.watson.ibm.com:/tmp/cvs-serv11900/src/exec/dpexec
Modified Files:
loader.c
Log Message:
Update to be able to build loadable modules correctly on AIX 4.2 and
higher. This eliminates compatibility with older systems but 4.1 is
at
Update of /src/master/dx/lib
In directory opendx.watson.ibm.com:/tmp/cvs-serv11900/lib
Modified Files:
Makefile.am
Added Files:
dxexec.imp
Log Message:
Update to be able to build loadable modules correctly on AIX 4.2 and
higher. This eliminates compatibility with older systems bu
Update of /src/master/dx/src/uipp/mb
In directory opendx.watson.ibm.com:/tmp/cvs-serv11900/src/uipp/mb
Modified Files:
MBGenerate.C Makefile.am
Log Message:
Update to be able to build loadable modules correctly on AIX 4.2 and
higher. This eliminates compatibility with older systems but 4.
Update of /src/master/dx/src/uipp/dxuilib
In directory opendx.watson.ibm.com:/tmp/cvs-serv11900/src/uipp/dxuilib
Modified Files:
ConfigurationDialog.C
Log Message:
Update to be able to build loadable modules correctly on AIX 4.2 and
higher. This eliminates compatibility with older systems
Hello,
I'm trying to loop the MRI_2.net demo from a script
file that the user only has to click once and then it
just goes. I've been able to get it to play, but not
to loop. If I enter dx -script and manually type it in
it works, but using echo to feed the prompt doesnt.
I'm pretty much stuck her
On Thu, 21 Aug 2003, David Thompson wrote:
> So you no longer need to set the -e flag to set the entry point?
No. When you build libraries that will be open with the "dlopen"
function, the entry point set with the -e flag will not be used. You
also do not need to set an entry point to DXEntry,
So you no longer need to set the -e flag to set the entry point? Does
the file dxexec.exp work as a -bE file if you change the first line
to #!. I guess what I'm asking is can you fix dxexec.exp to work for
both import and export? AIX is the only one that uses the .exp file.
What does the -G op
