Re: [ql-users] Drawing in the save area (SMSQ improvement)

2002-03-24 Thread ZN
On 3/18/02 at 9:14 AM Tony Firshman wrote: >> a) 'Regular' memory is generally quite substantially faster >> than screen memory > Wasn't it 30%? I forgot to answer this one - actually, it's closer to 50% when compared to true no-wait-state RAM on a standard QL. Things quickly get worse once an

Re: [ql-users] Drawing in the save area (SMSQ improvement)

2002-03-18 Thread Joachim Van der Auwera
> How does the second screen concept fit into all this? > ... sorry if you said but there was a _lot_ of text (8-)# It is not considered. However, this could easily be emulted by swapping the save area for another one and setting all the changed flags. Question is, whatfor? Which program needs thi

Re: [ql-users] Drawing in the save area (SMSQ improvement)

2002-03-18 Thread Tony Firshman
On Sun, 17 Mar 2002 at 18:17:21, ZN wrote: (ref: <[EMAIL PROTECTED]>) >Joachim wrote: > >> As I already mentioned, I am willing to volunteer for the following >> changes in SMSQ. >> >>- have all windows draw their contents in the save area >>- background update of windows (same mechanism) > >Yes

Re: [ql-users] Drawing in the save area (SMSQ improvement)

2002-03-17 Thread ZN
Joachim wrote: > As I already mentioned, I am willing to volunteer for the following > changes in SMSQ. > >- have all windows draw their contents in the save area >- background update of windows (same mechanism) Ye! :-) >In general I propose the following changes. >- Application should not

[ql-users] Drawing in the save area (SMSQ improvement)

2002-03-17 Thread Joachim Van der Auwera
As I already mentioned, I am willing to volunteer for the following changes in SMSQ. - have all windows draw their contents in the save area - background update of windows (same mechanism) In general I propose the following changes. - Application should not draw onscreen, but in the save area. W