Wolfgang Lenerz wrote:
>
> On 11 Jun 2001, at 22:42, FrançoisVan Emelen wrote:
>
> > Hi,
> >
> > It crashes with the usual qlib message window:
> > Job xx Col line 510 Q_LIB error 18
> > Array not DIMned
> > Data :512 1384 1 Stack:5000 852
>
Ian Pizer wrote:
>
> Hi All,
>
> With Windows mode, QPCII v2 Final will still not load. I get : The
> program has performed an illegal operation
> Details>> QPC2 caused an invalid fault in module QPC.exe at 0177:0040fc99
> etc. Perhaps that gives a clue?
Sometimes I get the same blue win
Wolfgang Lenerz wrote:
>
> On 11 Jun 2001, at 15:02, FrançoisVan Emelen wrote:
>
> > COL_obj works fine (even in mode 4) if you avoid pressing R,G,B (for red,
> > green, blue).
> Errm, why? What happens then?
>
> Wolfgang
Hi,
It crashes with the usual qlib m
Ian Pizer wrote:
>
> Hi Malcoln
>
> Thanks for your reply, but when using disp_colour 3 (start with "QL
> colours" for QPC2) anything tried closes QPC2.
> There is a program in Thierry Godefroy's web site called col.zip. Run in
> "QL colours" it does not work properly but could be interesting
Hi,
Thanks for the help on DATE and DATE$.
Special thanks to Tony,Nasta and Robert!
François Van Emelen
Hi,
Can someone explain this?
100 CLS
120 d=DATE(2001,6,11,0,0,0)
140 PRINT d
160 d1=1.2762214E9
180 PRINT DATE$(d)
120 PRINT DATE$(d1)
d1 is the value returned by d (line 140)
Why doesn't line 200 return the same date as line 180?
I tried different values for d in line 120 and changed line 160
Norman Dunbar wrote:
>
> It's turning into a better week now !
>
> I have now managed to solve the 'ambiguous name' errors with Qliberator when
> compiling Screen Snatcher. I had set dev2_ to be the location where I load
> and save to, and in the code, I had some $$asmb refernces to dev2_.
>
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,
Duncan Neithercut wrote:
>
> Hi
>
> Could the phantom black window be a default channel opened by using SCR_XLIM
> without any channels opened? This forces SMSQ/E to open a channel. You could
> check the size using the qpac2 Exec menu channels function?
>
> Duncan
Hi,
Well, I really can't t
Norman Dunbar wrote:
>
> Dear all,
>
> Firstly, QLiberator has behaved perfectly today - no compilation worries and
> no crashes on running. I wish I knew what was causing the problems :o(
>
> PER : I even managed to REDUCE the stack and heap size from 8K each to 4K
> stack and 2K heap as the
Norman Dunbar wrote:
>
> Someone said that the Easy pointer programs didn't work under high colour
> mode on QPC2v2 (or SMSQ) - I hate to contradict this, but mine works ok.
I did. But I didn't say none of them worked, I only mentioned
'Easysource_exe' and 'Easysprite_exe'.
Let's add some other
Geoff Wicks wrote:
> All the same there may be some problems in high collour mode with QLiberator
> compiled Easyptr programs. Versions of QL-Thesaurus prior to 4.02 crash in
> high colour mode with a parameter out of range message. This is a bit of a
> puzzle as the only parameter is the window
Norman Dunbar wrote:
>
> Yep here too.
> On NT4 service pack 6
> Running a registered copy of QPC2v2 and SMSQ version 2.98 (ver$(1))
>
> Following Dave's instructions to the letter ends up with a daughter job
> showing the no entry pointer.
>
> :o(
>
> Norman.
>
No problems here with Windo
Wolfgang Lenerz wrote:
>
> On 13 Mar 2001, at 10:46, FrançoisVan Emelen wrote:
>
> > No, can't repeat that.
>
> Ok, good.
>
> Thanks for answering.
>
> Could you tell me what version of smsqe you're using?
>
> Wolfgang
I'm using Smsqe
Wolfgang Lenerz wrote:
>
> Hello all
>
> I seemto have a curious problem is SMSQE Sbasic:
>
> Writing out the following lines:
>
> 10 def proc a(b,c%)
> 20 end def a
>
> and then:
>
> Qsave ram1_p
>
> followed by QLrun ram1_p
>
> crashes the copy of the basic interpreter.
>
> Can anyone
Peter Fox wrote:
>
> Is anyone else having problems with cursors? It looks as though my
> windows cursor is 'attached' to the QL cursor and is rewriting the screen
> as it goes along creating a mess.
>
> Regards,
>
> Peter Fox
Yes, I have., but only in 'always on top' not in 'window mode'.
I
16 matches
Mail list logo
