[EMAIL PROTECTED] makes some magical things to make me read
} Is it me, or was the GD2 standard supposed to allow each program to run at
} its own set colour depth and screen resolution, with the WMAN resetting these as
} you move between tasks..
It's probabbly you. At least GD2 sprite
In a message dated 12/11/2003 08:38:06 GMT Standard Time, [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] makes some magical things to make me read} Is it me, or was the GD2 standard supposed to allow each program to run at } its own set colour depth and screen resolution, with the WMAN resetting
Rich Mellor wrote:
The problem with writing these programs is if you want to change the
screen colour depth and resolution to fit your application (why
should QWord use the standard QL colours on QPC2 when it can switch
into high colour mode).
IMHO, a program should *never* change the
John Hall makes some magical things to make me read
} Rich Mellor wrote:
}
} The problem with writing these programs is if you want to change the
} screen colour depth and resolution to fit your application (why
} should QWord use the standard QL colours on QPC2 when it can switch
} into
IMHO, a program should *never* change the colour depth or screen
resolution without the user's express permission!
If I'm running QPC2 in, say, 800x600 QL colour mode, it's for a
reason. The last thing I want is for a program to take it upon
itself
to change things, especially since a
[EMAIL PROTECTED] wrote:
The problem with writing these programs is if you want to change the
screen colour depth and resolution to fit your application (why
should QWord use the standard QL colours on QPC2 when it can switch
into high colour mode).
What it should do is write Must be run in
John Hall wrote:
IMHO, a program should *never* change the colour depth or screen
resolution without the user's express permission!
If I'm running QPC2 in, say, 800x600 QL colour mode, it's for a
reason. The last thing I want is for a program to take it upon
itself
to change things,
[EMAIL PROTECTED] a écrit:
Is it me, or was the GD2 standard supposed to allow each program to run
at its own set colour depth and screen resolution, with the WMAN
resetting these as you move between tasks..
IIRC this was the subject of a long thread about problems/solutions but
long
Arnould Nazarian wrote:
At this occasion Marcel even told us that in the Windows world it is up
to the applications to redraw screens.
This is basically the case on all systems other than SMSQ/E.
I do'nt know anything about programming Windows, but I remember very
correctly that I was
Well, why should Windows save 2 Megabyte of screen memory for a simple
editor if the few bytes of the text plus a few bytes of a routine that
draws the text on screen can do just fine, too?
Anyway, it's not unproductive code. You just write your code in a way
that it can not only draw your stuff
Arnould Nazarian wrote:
OK, but it is preferrable that the programmer does not forget to
call that code everytime it is needed.
Actually the code is called by Windows whenever it's needed.
In pseudo-SBasic a Hello World app would look somewhat like this:
REMark Simple hello world application
On 11 Nov 2003 at 19:26, Marcel Kilgus wrote:
(...)
BTW: If anybody is waiting for some private mail from me, I'm coming
to that. Currently I'm dead tired.
More tired than dead, I hope...
Wolfgang
Is it me, or was the GD2 standard supposed to allow each program to run at its own set colour depth and screen resolution, with the WMAN resetting these as you move between tasks..
This would be a really nice feature - it is particularly noticeable in QWord, which uses the GD2 colour
13 matches
Mail list logo
