www.delorie.com/archives/browse.cgi | search |
From: | "Maan M. Hamze" <mmhamze AT mail DOT utexas DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Run...Run bug in RHIDE 1.1? |
Date: | 24 Jan 1997 05:04:32 GMT |
Organization: | University of Texas at Austin |
Lines: | 23 |
Message-ID: | <01bc09b3$205a0e20$756f5380@maan-m.-hamze> |
References: | <01bc08e4$a6a61840$76db5380 AT maan-m DOT -hamze> <32E75660 DOT 67CB AT Mathematik DOT tu-chemnitz DOT de> |
NNTP-Posting-Host: | slip-30-5.ots.utexas.edu |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Robert Hoehne <Robert DOT Hoehne AT Mathematik DOT tu-chemnitz DOT de> wrote in article <32E75660 DOT 67CB AT Mathematik DOT tu-chemnitz DOT de>... > Maan M. Hamze wrote: > > > With a program that needs user's input (through cin for example) this can > > be quite an inconvience. > > Is there a fix for this? > I don't know where your problem is. Can you explain it a little bit > more? Actually Robert you answered that in another thread, so I have the answer now. I was inquiring about the possibility of keeping the program output screen (from Run..Run) visible. Right now it opens and closes again. My suggestion was to prompt the user to press a key to go back to RHIDE. So the user can inspect the output of the program through Run..Run. I believe I have the answers to what I was inquiring about. Thanks! Maan -- Maan M. Hamze mmhamze AT mail DOT utexas DOT edu http://leb.net/~mmhamze
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |