Re: [ql-users] WMAN progress

2002-11-29 Thread Phoebus Dokos
??? 29/11/2002 8:37:09 ??, ?/? Marcel Kilgus <[EMAIL PROTECTED]> ??: > >Third attempt to send this mail. At least none of the first two came >back to me. > >Joachim Van der Auwera wrote: >> The slower loading is mainly caused by the precalculated fonts. When ProWesS >> is configured to have n

Re: [ql-users] WMAN progress

2002-11-29 Thread Marcel Kilgus
Third attempt to send this mail. At least none of the first two came back to me. Joachim Van der Auwera wrote: > The slower loading is mainly caused by the precalculated fonts. When ProWesS > is configured to have no precalculated fonts, the system will be much > faster. This would however affect

Re: [ql-users] WMAN progress

2002-11-29 Thread P Witte
Wolfgang Lenerz writes: > yu can also do that with wm.rptrt (vector $78), which allows a > timeout (much easier!) This is the way FiFi handles the small help > windows. This is not documented anywhere in my Qptr manual!! (3rd revision) so its the first I hear of it. It looks like its been in the

Re: [ql-users] WMAN progress

2002-11-29 Thread Bill Waugh
- Original Message - From: "Phoebus Dokos" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 29, 2002 5:37 AM Subject: Re: [ql-users] WMAN progress ??? 28/11/2002 11:47:26 ??, ?/? François Lanciault <[EMAIL PROTECTED]> ??: > >It is the 'Many people' that I don't a

Re: [ql-users] WMAN progress

2002-11-29 Thread Wolfgang Lenerz
On 29 Nov 2002, at 4:18, [EMAIL PROTECTED] wrote: > WM.RPTR does a lot of work for the programmer, but has a fairly > complicated way of monitoring the position of the pointer and any > mouse clicks/keystrokes. > > I wanted to do two things. > (...) b. > Produce the little explanatory windows

Re: [ql-users] pointer programming

2002-11-29 Thread Geogwilt
In a message dated 28/11/02 06:48:36 GMT Standard Time, [EMAIL PROTECTED] writes: One caution for 'C' coders - if you are using the new GD2 calls and the message passing routines that are available in C68, I have found that several of the 'C' wrappers that call the native assembly routines are

Re: [ql-users] WMAN progress

2002-11-29 Thread Geogwilt
In a message dated 27/11/02 14:34:17 GMT Standard Time, [EMAIL PROTECTED] writes: > >A better way would be a menu designer for QPTR, of course... >Would also make it easier for Assembler programmers > >(...) >> * I hope all this makes sense ;) > >It does to me. > Well THERE'S GOT TO BE an eas

Re: [ql-users] WMAN progress

2002-11-29 Thread Fabrizio Diversi
--- Phoebus Dokos <[EMAIL PROTECTED]> wrote: > > Well on the Q40 (at least mine) I tried to load it > and it's impossible to get it to > work. It seems that some bugs were re-introduced on > SMSQ/E v.2y99 (I just found > out) that makes it impossible to work... or maybe > it's just my system..

Re: [ql-users] WMAN progress

2002-11-29 Thread Geogwilt
In a message dated 26/11/02 17:26:31 GMT Standard Time, [EMAIL PROTECTED] writes: iop.rptr does if you set the appropriate bits in the return vector. But Wman calls (wm.rptr) only respond to "events" (see the Qptr manual, pages 89 ff "Window Manager Access Routines") WM.RPTR does a lot of work

Re: [ql-users] WMAN progress

2002-11-29 Thread Wolfgang Lenerz
On 28 Nov 2002, at 12:15, TonyTebby wrote: (...) > There are other simpler methods. How about > > alert('Hello World') (Javascript) Wouldn't you need something like (...) around it? (makes everything longer) How about: open#3,"con" print#3,'Hello World' > Perhaps instea