Re: [cc65] conio tabs

>>>>> "G" == Groepaz  <groepaz@gmx.net> writes:

Uz> So the question is: Do we want to change the design criterias
Uz> behind conio? Of course it can be improved. I've already
Uz> considered adding a cscroll() function which allows scrolling -
Uz> not automatically, but when requested by the programmer. This
Uz> seems to fit better into the current conio design. But adding
Uz> automatic scrolling and tab interpretation do change the idea
Uz> behind conio, and so before adding anthing like that, I would like
Uz> to discuss if this is really what we want.

G> i would vote against tab interpretation and scrolling, IF there is
G> a seperate function to allow scrolling arbritary sections of the
G> screen in any direction. that would be much more useful in the end,
G> and keep the rest of the api small and clean and fast. (and uhm,
G> who really needs tabs?)

I'm voting for it. The point of the library is to make it convenient
to do text output, and having it overwrite memory and crash the
program because you do one cprintf statement too much (something
that's bitten me more than once) isn't very elegant. Having to
manually check where the cursor is after every print statement, to see
if we need to call cscroll, sounds kinda clunky. In some apps multi-
directional region scrolling would be better, in some apps simple
screen scrolling is all you need.

-- 
    ___          .     .  .         .       . +  .         .      o   
  _|___|_   +   .  +     .     +         .  Per Olofsson, arkadspelare
    o-o    .      .     .   o         +          MagerValp@cling.gu.se
     -       +            +    .     http://www.cling.gu.se/~cl3polof/
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.