Re: [ql-users] Phantom black con channel in QLiberated programs - SOLVED !
Dilwyn Jones wrote: > SCR_XLIM and SCR_YLIM most probably call iop.flim trap No. They just need the channel block in order to find the address of the PTR/CON linkage. From then on it's one simple MOVE command. So it's not really an "official" way of doing it. > The SMSQE manual I have hints at this but doesn't fully clarify it. > SCR_BASE and SCR_LLEN are described as accepting channel numbers, > SCR_XLIM and SCR_YLIM are not, Oh, you've another manual (ok, I didn't expect you to have a German manual anyway). My version tells me that the optional channel parameter for all functions. > but the description refers to maximum size windows can be set to > rather than screen size as such, implying the behaviour of an > iop.flim type extension. No, it's always the screen size. Marcel
Re: [ql-users] Phantom black con channel in QLiberated programs - SOLVED !
>> why not simply use >> >> open#x, con >> scr_xlim#x > >is it documented somewhere? > SCR_XLIM and SCR_YLIM most probably call iop.flim trap and this in turn needs an open window - it returns the maximum possible outline of a channel - this corresponds to maximum screen size if it's a primary channel (e.g. #0 in BASIC), or the maximum outline that the secondary windows can be set to within that primary. Most extensions I've seen which return max screen dimensions call iop.flim (I wrote one such pair of extensions FLIM_W and FLIM_H in the DISPLAY_CDE article in a past QL Today), and all need either an open channel to test, or if none supplied open a channel themselves. After Marcel's comments, I'm sure we can assume that SCR_XLIM and SCR_YLIM work in pretty much the same way as others I've seen. The SMSQE manual I have hints at this but doesn't fully clarify it. SCR_BASE and SCR_LLEN are described as accepting channel numbers, SCR_XLIM and SCR_YLIM are not, but the description refers to maximum size windows can be set to rather than screen size as such, implying the behaviour of an iop.flim type extension. -- Dilwyn Jones [EMAIL PROTECTED] http://www.soft.net.uk/dj/index.html
Re: [ql-users] Phantom black con channel in QLiberated programs - SOLVED !
> On 29 Mar 2001, at 13:27, Norman Dunbar wrote: > > > What to do to avoid a phantom : > > > > 1. Compile with windows copied. > > 2. Open #0 or #1 before calling scr_xlim/scr_ylim > > > > I suspect therefore that scr_xlim/scr_ylim look for channel #0 first and if > > found use it. > > If #0 not found, then try #1 and if found use it. > > If #0 and #1 not found, open a new #0 and use that. This channel appears to > > stay open until the end of the job. > > > why not simply use > > open#x, con > scr_xlim#x is it documented somewhere? Bye Richard
RE: [ql-users] Phantom black con channel in QLiberated programs - SOLVED !
>> why not simply use >> open#x, con >> scr_xlim#x >> Wolfgang Ah well, at the time I didn't know about the channel id parameter. :o( But Marcel pointed it out this morning - so I do now :o) Thanks. Norman. Norman Dunbar EMail: [EMAIL PROTECTED] Database/Unix administrator Phone: 0113 289 6265 Lynx Financial Systems Ltd. Fax:0113 201 7265 URL:http://www.LynxFinancialSystems.com
Re: [ql-users] Phantom black con channel in QLiberated programs - SOLVED !
On 29 Mar 2001, at 13:27, Norman Dunbar wrote: > What to do to avoid a phantom : > > 1. Compile with windows copied. > 2. Open #0 or #1 before calling scr_xlim/scr_ylim > > I suspect therefore that scr_xlim/scr_ylim look for channel #0 first and if > found use it. > If #0 not found, then try #1 and if found use it. > If #0 and #1 not found, open a new #0 and use that. This channel appears to > stay open until the end of the job. > why not simply use open#x, con scr_xlim#x Wolfgang
RE: [ql-users] Phantom black con channel in QLiberated programs -SOLVED !
Nope, I had everything loaded that I had loaded before I changed #3 into #0 :o( I feel the need to swot up on Turbo again. I shall send you a current (complete with phantoms) copy of SS3 by separate post - and hopefully, when I get it fixed, you can have a copy then as well. Norman. Norman Dunbar EMail: [EMAIL PROTECTED] Database/Unix administrator Phone: 0113 289 6265 Lynx Financial Systems Ltd. Fax:0113 201 7265 URL:http://www.LynxFinancialSystems.com -Original Message- From: FrançoisVan Emelen [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 29, 2001 4:50 PM To: [EMAIL PROTECTED] Subject: Re: [ql-users] Phantom black con channel in QLiberated programs -SOLVED ! Didn't you forget to LRESPR the easyptr extensions aftez a reset? Did you include REMark $$asmb=device_drectory_YourExtensions_cde,4,82? François Van Emelen P.S. Can I have a copy of SS3?
Re: [ql-users] Phantom black con channel in QLiberated programs -SOLVED !
Norman Dunbar wrote: > > Argh ! > > After amending all the #3s in Screen Snatcher to #0s to get rid of the > Phantoms, I'm now unable to compile because all my EP3 copmmands are giving > 'Ambiguous Name' error messages again ! > > Regards, > > Confused even more of Bradford. > Hi, Didn't you forget to LRESPR the easyptr extensions aftez a reset? Did you include REMark $$asmb=device_drectory_YourExtensions_cde,4,82? François Van Emelen P.S. Can I have a copy of SS3?
RE: [ql-users] Phantom black con channel in QLiberated programs - SOLVED !
Argh ! After amending all the #3s in Screen Snatcher to #0s to get rid of the Phantoms, I'm now unable to compile because all my EP3 copmmands are giving 'Ambiguous Name' error messages again ! Regards, Confused even more of Bradford. Norman Dunbar EMail: [EMAIL PROTECTED] Database/Unix administrator Phone: 0113 289 6265 Lynx Financial Systems Ltd. Fax:0113 201 7265 URL:http://www.LynxFinancialSystems.com
[ql-users] Phantom black con channel in QLiberated programs - SOLVED !
I have written a small test program which opens a channel and reads the values of scr_xlim & scr_ylim, prints them and then closes the channel. When compiled with windows copied, there is no phantom - ever ! When compiled with no windows copied, the phantom appears under the following circumstances 1. The calls to scr_xlim/scr_ylim are made before the window is opened 2. The calls are made after opening, and the channel opened is not #0 or #1. (#2 onwards will show the phantom.) 3. The call is made before opening #0, briefly shows a phantom which vanishes as soon as #0 opens. 4. The call is made before opening #1, shows a phantom which doesn't vanish as soon as #1 opens. What to do to avoid a phantom : 1. Compile with windows copied. 2. Open #0 or #1 before calling scr_xlim/scr_ylim I suspect therefore that scr_xlim/scr_ylim look for channel #0 first and if found use it. If #0 not found, then try #1 and if found use it. If #0 and #1 not found, open a new #0 and use that. This channel appears to stay open until the end of the job. Hope this helps other sufferers. Norman. Norman Dunbar EMail: [EMAIL PROTECTED] Database/Unix administrator Phone: 0113 289 6265 Lynx Financial Systems Ltd. Fax:0113 201 7265 URL:http://www.LynxFinancialSystems.com