I can see you have a lot of experience in this type of
thing. I was hoping to run Qpro and bring up reciepts
that had been scanned and view them with quickview or PV.
I run dos mostly to use qpro; a link to quickview would
add alot to qpro. A fast way to review numbers.

Many thanks.

cheers
DS



On Tue, 1 Oct 2019 19:08:22 -0400 dmccunney <dennis.mccun...@gmail.com>
writes:
> On Tue, Oct 1, 2019 at 4:03 PM Dale E Sterner <sunbeam...@juno.com> 
> wrote:
> >
> > Dennis
> >
> > I think you were saying that TCL was used to link programs 
> together.
> 
> Well, to tie them together.  Linking is a different thing.  You can
> think of TCL as a vastly more powerful version of a batch file,
> calling other programs from the script with execution guided by the
> results of previous calls.  (In DOS batch you can use things like 
> "if
> errorlevel" to determine the success or failure of a previous 
> process
> and do different things depending on whether or not the previous
> program succeeded.  Of course, this requires the programs you run 
> exit
> with a return code that DOS can store and access. Not all did.)
> 
> In Don Libes' Expect application written in TCL, I could to things
> like use TCL to spawn an application to communicate to a remote host
> that expected interactive execution, and use the TCL "expect" 
> command
> with a parameter of *what* to expect to grab the prompt from the 
> host
> and do the next thing needed in response, so I could log on to the
> remote host and run commands on it and collect results 
> automatically,
> and not have to be manually controlling the process.  (I had one job
> that ran at midnight, connected to a Unix host, and collected job
> status reports which it then sent along to an NT server that was
> accessible from the outside world so the clients could see the 
> status
> of what we were doing for them.  We *weren't* comfortable opening
> ports on our firewall to let them get directly to the Unix server, 
> and
> it wasn't necessary.  Just put the reports on a server they *could*
> get to and let them grab them.  And this happened automatically 
> while
> we all slept.
> 
> > Is it possible to use it to link qpro to quickview.
> > Could I open quickview while runing qpro.
> > If anyone would know it would be you.
> 
> Under a multi-tasking OS like Linux or Windows, likely.  Under a
> single tasking OS like DOS, likely *not*.
> 
> If it could be done, it would require suspending Qpro and opening
> Quickview.  I recall doing things like that in DOS using TSRs, where
> the TSR display opened over what the running program had on screen.
> The currently running program was suspended while the TSR ran, and
> when you left the TSR, execution resumed on the underlying program.
> Unless Quickview can be implemented as a TSR to pop up over QPro, I
> don't see this working.  And I assume you would want to do it
> interactively, and press something like a hotkey combo to pop up
> Quickview.  TCL can't do that for you.  It's intended for 
> *unattended*
> processing.
> 
> I'm afraid TCL isn't the tool for the job you want to do.
> 
> > cheers
> > DS
> ______
> Dennis
> 
> 
> _______________________________________________
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
> 


******************************************************>>>>
>From Dale Sterner - MS organic chemistry
http://pubs.acs.org/doi/abs/10.1021/jo00975a052
*******************************************************>>>>

____________________________________________________________
All Natural "Miracle Oil" Works Wonders! (Now Legal)
onedaytorunlive.com
http://thirdpartyoffers.juno.com/TGL3141/5d94f72b6a793772b0b87st03duc


_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to