From mint-bounce@lists.fishpool.fi Tue Dec 8 07:51:18 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=6MLe/YD9tIBIRDeRvb9B0eWxCmXcVn70+dltoVYJFCU=; b=NfL6C05+7CHSSWxUMvJ6LiNtXuW0foVEbIEth9KecOmWPoOEpgD2bI3NvmaAcpGxQb 2DEOp7eD5Oci0I/3J4bKGXalV1PEZYlbkhtFdrgrkJWlrEIyU5u7dk/ckTrOTKrVMosm EzO55W32Xs/tX9DZraDZqdXfL930PF0xj/00A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=Zkweq3sdT9/rM655Zvyk3BxESuZGcbYlPCr9VrUVcoJWP+/P3V+JPXr/hy3lafjxjP FwXEjpNyoBgnxUYYxgx7zIPI8dbKho6e6ritLSze9QCZmYOR9zpBsaliPqEk6JGJ4rKQ s4chQp9P0ZVFD1cTV5jYwrdwbYGsIdLrGTW8U= MIME-Version: 1.0 In-Reply-To: References: <11a6f2b10911270646s6ceab50i915d71aeb27f6be9@mail.gmail.com> <11a6f2b10911281010t6c5780abnc26d088776ab1afd@mail.gmail.com> <11a6f2b10911281226n17c678c2q9052207e62206518@mail.gmail.com> <11a6f2b10911281304o32549012oae0b09887d570c05@mail.gmail.com> <11a6f2b10911281336q6ad74b7au657ac40469b28d8@mail.gmail.com> Date: Tue, 8 Dec 2009 13:47:54 +0100 X-Google-Sender-Auth: 5fe4ffb69fff0559 Message-ID: Subject: Re: [MiNT] XaAES sources for FreeMiNT 1.16.3 From: Johan Klockars To: Helmut Karlowski Cc: "mint@lists.fishpool.fi" Content-Type: text/plain; charset=ISO-8859-1 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: johan@klockars.net Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: >> I don't understand why no one ever seems to use vq_scrninfo(). If it >> has problems on some hardware, that should be easy to patch. Applying > > As you probably know, I posted possible fvdi-issues for months on this list, > but none was cured as far as I know. So I'm just looking for ways to get it > running as is. Well, I'm not reading this list all the time, and certainly don't often have time to look into "possible issues" with it. Still, the code is available and you're free to tell me what is wrong with it, or fix it yourself. I am aware of one issue that has been pointed out to me, concerning the clipping of italic text, but I don't seem to ever get around to doing anything about it... >> However, the real problem is that you keep getting 11101 rather than >> 11111 for what should be maximum colour values. > > All the bits-analysis is nonsense: These are random-numbers (I needed Uhm. They certainly are not random. You don't just _happen_ to get 11101 (instead of the 11111 you would expect) for every single maxed out colour component in whatever combination. > more than an hour to find this). Please read the thread about > pixel-detection. If you are talking about how vs_color() supposedly does not work for non-CLUT colour modes, that is nonsense. How would you expect any application whatsoever to be able to use any colour not in the standard palette on a true colour screen? What vs_color() will not do on a true colour screen is change the colour of any pixel alread on the screen, since the palette it is setting is just a virtual one (there must still be a palette/CLUT, just a software based, or the VDI would be unusable). Still, anything drawn using that palette index (on that specific virtual workstation) afterwards will certainly use the new colour you just set. See for example http://toshyp.atari.org/007004.htm#vs_color. > Sure there are differences, in the initialization before the > pixel_format-test. > But I've found nothing that's obviously wrong. And as the used method is not > allowed anyway, I don't search any longer. This is just academic. So, how would you set which colours to use, if not via vs_color()? I'm not claiming anything about the rest of whatever XaAES does, but setting the colour via vs_color() is the only way to do it. If that did not work, the only way you would be able to go outside the default palette on a true colour display would be via vro_cpyfm()... /Johan