In a message dated 04/01/2004 21:57:09 GMT Standard Time,
[EMAIL PROTECTED] writes:
I have the same boot file on my Q40 as my qpc2. But my qpac2
buttonbar is placed in the middle of the screen on qpc2. I want it in the
top left corner.
Could be that QPAC2 is not configured in the same way o
Hi
I have the same boot file on my Q40 as my qpc2. But my qpac2
buttonbar is placed in the middle of the screen on qpc2. I want it in the
top left corner.
/Michael
- Original Message -
From: "Dilwyn Jones" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, January 04, 2004 4:16 PM
Subject: Re: [ql-users] QL Documentation
>
> > >> >Not all of the material is there yet, but it's a hug improvement
> > >> That is almost as good as "QL Toady".
Hi all, hope you had a good break! (As did I ;)
Now to business: I want to update a couple of my PE programs to the new wman
standard. The first obstacle I encountered was sprites/icons. What a bummer
to have to design those bloomin things - as if writing programs wasnt
enough!
Thanks to Wolfgan
> >> >Not all of the material is there yet, but it's a hug improvement
> >> That is almost as good as "QL Toady". Are you trying to say
'big'
> >is
> >> huggable (8-)#
> >I'm big, I'm definitely huggable (says my wife).
> Can you leave me out of the queue though please (8-)#
:-)
> >Next competit
George Gwilt writes:
> As everyone will realise by now, the events given to WM.RPTRT in D2.B are
job
> events, not pointer events. So, obviously, WM.RPTRT will return on any
> pointer event just as WM.RPTR does whatever the value in D2.B.
Sorry I wasnt more helpful but Ive been extermely busy be
Phoebus R Dokos wrote:
> I have it on good authority that Sears discontinued that item after
being
> the recipient of a class-action suit. The problem (as documents are
> sealed) is rumored to be low-mileage before the nagging point ;-)
Others
> claim that costs for out-of-warranty repairs were ve
On 2 Jan 2004 at 11:51, [EMAIL PROTECTED] wrote:
(...)
>
> Since the original IOP.RPTR asks for D2.B to be set, does this not mean that old
> programs
> calling the routine might find peculiar things happening? For example, the contents
> of D2.L could
> have $FF as the top byte. D2 might hav
