Re: 4js-D4gl: RUN another program from menu system replaces menu window?

On Tue, 16 Feb 1999, Andrej Falout wrote: > when we use "central" program to serve as menu system for running other programs in > the application (with something like "RUN 'fglrun abc.42r'"), GUI window of menu > application on the client PC is replaced with that application's window. > > I would like to have menu app constantly open, and active, so that user can run > another program from menu app without the need to close currently running program, or > open another menu application. > > I think I have seen this working like that before somewhere, but now I'm not sure how > to achieve this. > > In short, is there a way to preserve the window of app that is calling another app > with RUN statement? I think you have to use RUN WITHOUT WAITING or WinExec (as opposed to RUN or WinExecWait). I also think you have to ensure that the run application uses a different FGLSERVER value, thus chewing up another user licence. I haven't formally verified this, but I would expect it to allow me to run d4glapp1 into window1 and simultaneously have d4glapp2 running to window2. If the applications share the same FGLSERVER, then only one of them can meaningfully be active at one time. Yours, Jonathan Leffler (jleffler@informix.com) #include <wish/I/was/skiing.h> Guardian of DBD::Informix v0.60 (v0.61_02) -- http://www.perl.com/CPAN Informix IDN for D4GL & Linux -- http://www.informix.com/idn

On Tue, 16 Feb 1999 16:51:39 -0800 (PST), Jonathan Leffler <jleffler@informix.com> wrote: > >On Tue, 16 Feb 1999, Andrej Falout wrote: >> when we use "central" program to serve as menu system for running other programs in >> the application (with something like "RUN 'fglrun abc.42r'"), GUI window of menu >> application on the client PC is replaced with that application's window. >> >> I would like to have menu app constantly open, and active, so that user can run >> another program from menu app without the need to close currently running program, or >> open another menu application. >> >> I think I have seen this working like that before somewhere, but now I'm not sure how >> to achieve this. >> >> In short, is there a way to preserve the window of app that is calling another app >> with RUN statement? > >I think you have to use RUN WITHOUT WAITING or WinExec (as opposed to RUN >or WinExecWait). I also think you have to ensure that the run application >uses a different FGLSERVER value, thus chewing up another user licence. I >haven't formally verified this, but I would expect it to allow me to run >d4glapp1 into window1 and simultaneously have d4glapp2 running to window2. >If the applications share the same FGLSERVER, then only one of them can >meaningfully be active at one time. Use RUN WITHOUT WAITING and no - you don't need to change FGLSERVER to use both applications at the same time. The clients are able to handle more then one application at the same time. Ralf -- e-mail: ralf@bj-ig.de Van Roy's Law: ------------------------------------------------------- An unbreakable toy is useful for breaking other toys.

Alternatively use QueriX 4GL you do not even have to use the TKL stuff. goto www.querix.com Ralf Mueller wrote: > On Tue, 16 Feb 1999 16:51:39 -0800 (PST), Jonathan Leffler <jleffler@informix.com> wrote: > > > >On Tue, 16 Feb 1999, Andrej Falout wrote: > >> when we use "central" program to serve as menu system for running other programs in > >> the application (with something like "RUN 'fglrun abc.42r'"), GUI window of menu > >> application on the client PC is replaced with that application's window. > >> > >> I would like to have menu app constantly open, and active, so that user can run > >> another program from menu app without the need to close currently running program, or > >> open another menu application. > >> > >> I think I have seen this working like that before somewhere, but now I'm not sure how > >> to achieve this. > >> > >> In short, is there a way to preserve the window of app that is calling another app > >> with RUN statement? > > > >I think you have to use RUN WITHOUT WAITING or WinExec (as opposed to RUN > >or WinExecWait). I also think you have to ensure that the run application > >uses a different FGLSERVER value, thus chewing up another user licence. I > >haven't formally verified this, but I would expect it to allow me to run > >d4glapp1 into window1 and simultaneously have d4glapp2 running to window2. > >If the applications share the same FGLSERVER, then only one of them can > >meaningfully be active at one time. > > Use RUN WITHOUT WAITING and no - you don't need to change FGLSERVER to use > both applications at the same time. The clients are able to handle more > then one application at the same time. > > Ralf > > -- > e-mail: ralf@bj-ig.de > Van Roy's Law: ------------------------------------------------------- > An unbreakable toy is useful for breaking other toys.

Alternatively write it in Java and you can avoid the client licence fees altogether. Since the answer below didn't address the point either.... On Wed, 17 Feb 1999 12:50:56 +0000, Peter Ross <peterross@hotmail.com> wrote: >Alternatively use QueriX 4GL you do not even have to use the TKL stuff. > >goto www.querix.com > >Ralf Mueller wrote: > >> On Tue, 16 Feb 1999 16:51:39 -0800 (PST), Jonathan Leffler <jleffler@informix.com> wrote: >> > >> >On Tue, 16 Feb 1999, Andrej Falout wrote: >> >> when we use "central" program to serve as menu system for running other programs in >> >> the application (with something like "RUN 'fglrun abc.42r'"), GUI window of menu >> >> application on the client PC is replaced with that application's window. >> >> >> >> I would like to have menu app constantly open, and active, so that user can run >> >> another program from menu app without the need to close currently running program, or >> >> open another menu application. >> >> >> >> I think I have seen this working like that before somewhere, but now I'm not sure how >> >> to achieve this. >> >> >> >> In short, is there a way to preserve the window of app that is calling another app >> >> with RUN statement? >> > >> >I think you have to use RUN WITHOUT WAITING or WinExec (as opposed to RUN >> >or WinExecWait). I also think you have to ensure that the run application >> >uses a different FGLSERVER value, thus chewing up another user licence. I >> >haven't formally verified this, but I would expect it to allow me to run >> >d4glapp1 into window1 and simultaneously have d4glapp2 running to window2. >> >If the applications share the same FGLSERVER, then only one of them can >> >meaningfully be active at one time. >> >> Use RUN WITHOUT WAITING and no - you don't need to change FGLSERVER to use >> both applications at the same time. The clients are able to handle more >> then one application at the same time. >> >> Ralf >> >> -- >> e-mail: ralf@bj-ig.de >> Van Roy's Law: ------------------------------------------------------- >> An unbreakable toy is useful for breaking other toys. >