From mint-bounce@lists.fishpool.fi Mon Dec 7 23:54:53 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=oauyez+MBihBsUngpIQIbBF5flamWwhUJ+ZYliUkRTg=; b=CXNCUOcQRhI+1rI3tt5D09b55vk3gSwk7mrbPzl7c95f9hHBKBtmP0mgJPsgcC9Fd1 cor/rV7LsCJkJuH78fJq5qAEwdxAM5id8iyGdND/7ImXaM4OaQyOCb1wVENdqzNG9gKC 8dRTDHdk9R80b3s79oR4qKga/j0N0aC/EGRzM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Q4yUFo7IcPUKmopMcDZR4D1P34mRzPJeyxhrF//zIybA9HF9lfZB8+sqKZ04byyme3 GH02UxGSYOQroz8t985YN0H22GR13c6BkHfvHBJYPEuQr65Y8/ToLUWKl/gK8XNTRYsC OY1gRAZFzwiDj6oz+y54I1qIk780xkLLMkwww= 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> <11a6f2b10912070147g2fbbe909u466a57ae8b89456c@mail.gmail.com> Date: Tue, 8 Dec 2009 15:51:06 +1100 Message-ID: <11a6f2b10912072051s2ebcefc5r20a7856c02e66fa3@mail.gmail.com> Subject: Re: [MiNT] XaAES sources for FreeMiNT 1.16.3 From: Paul Wratt To: mint 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: paul.wratt@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: On Tue, Dec 8, 2009 at 8:01 AM, Helmut Karlowski wrote: > Am 07.12.2009, 10:47 Uhr, schrieb Paul Wratt : > >> I seriously lean toward this idea, simply because current builds of >> MiNT & XaAES (1.17) are not usable in ARAnyM. > > You cannot claim that XaAES isn't usable just because of that > pixel-detection! > this is NOT pixel detection problem: http://paulwratt.110mb.com/atarist/mint/1.17-cur/cvs-20090828/ I had already posted that link.. >> BTW I get E0E000 for red+green > > Anyone has some more? ;-) > it does not fix the pixel detection problem, just allow recognition of non FFFF00 returns. There are already functions that cover "standard" pixel formats and convertion.. this would mean having individual pixel related routines for each and every variation, which was NOT nessescary with XaAES in 1.16. If the pixel detection (screen or texture) had any serious flaws, it would have shown up before now, and before 1.16.3 dev was discontinued.. >> Again, how does use of "vq_scrninfo()" in XaAES impact on MiNT when > > MiNT has nothing to do with vq_scrninfo. > out of context.. see.. >> used with other VDI's. XaAES is going through some upgrades and bug > > vq_scrninfo could be used in the next version if there is fvdi, else > the old method that seems to work with nvdi. But I already suggested a > possible way for all. In the end a working vq_scrninfo should be supplied > for all VDIs like Lonny suggested. > > -Helmut > It seems NVDI is the main reason as to why "vq_scrninfo" is not used, so yes it should be "fixed" in some way BTW what is the likelyhood of getting NVDI sources (is there a need, with fVDI still being developed, or is pass-thru for printer support still valid) Helmut: I get the feeling that Johan has not been on this list, at least not while you have be posting, until now.. Paul