From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,bd9ba71376053a01 X-Google-Attributes: gid103376,public From: Ron Thompson Subject: Re: how to put cursor at X,Y Date: 1996/10/31 Message-ID: <55aeve$idh@faatcrl.faa.gov>#1/1 X-Deja-AN: 193533194 references: <3270BBC4.5480@univ-orleans.fr> <556euh$opl@felix.seas.gwu.edu> <1996Oct30.074712.1@corning.com> content-type: text/plain; charset=us-ascii organization: aos-420 mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 1.2 (Windows; U; 32bit) Date: 1996-10-31T00:00:00+00:00 List-Id: The brave Ada programmer is always hammered about the apparent lack of screen handling capabilities in the typical Ada environment. A lot of money and you can't even do this... etc. You know what I mean. I used to do the ansi.sys way. It was excellent exercise for the programmer to understand what exactly it takes to control the NON graphics mode of the typical Intel pc screen. Later, I started using the mapped array, with the first address being the starting address of the bios screen. A word per address, with the bits defined as the standard bios interface, whammmo, refresh rate screen handling that is unsurpassed in the dos world. Can't do it in winders, winders MUST do all of that stuff for you I suppose. But for the brave dos programmers, let me know and I will help you build a sporty screen interface that is as fast as the machine allows. rct The opinions above are mine and mine alone.