steb@gcad.doit.wisc.edu wrote: >mwalker@consult.caci.co.uk (Martin Walker) writes: >>steb@gcad.doit.wisc.edu wrote: >(snip) >>To get a G.U.I display the termcap entry used by your ABF app must be >>m0. The m0 termcap entry has the "mw" property set and this will tell >>the host to communicate in G.U.I mode. >>One common problem faced by users logging onto upfront is that whilst >>they set TERM_INGRES m0 in there login script, the script that runs >>their ABF application then resets TERM_INGRES to a standard terminal. >> >>Hope this helps. >> >>Martin Walker - Chief Architect The UpFront Team. >Unfortunately, if I use the m0 termcap setting, our abf application refuses to >run saying that there is no such entry in the termcap. It is there, and I then >set TERM_INGRES to mws (the second heading for that termcap entry) and this >is when the app will run, if only in text mode. I'll probably continue to argue >with it today and maybe through the end of the week. If I can't get it running >easily, it'll have to come off as I don't have the time to futz with it. >Thanks for your suggestions, I appreciate it. >William A. Barnett-Lewis >*standard_disclaimers* What you should have written/set in your termcap file is the following m0|mws|MacWorkStation: :mw:ky: :mf=upfront.map: :co#80:li#24: :kn#40:tc=vt100nk: This information and more if needed can be found in the Upfront Help files under the title CA-Ingres Keyboard Mapping. And as my colleague Martin already pointed out make sure that you are not resetting the TERM_INGRES flag whilst running your app via a script/profile.
© William Yuan 2000
Email William