RE: Re: Fullscreen application Specs

Very nice
 
That you are reading the code and resolving bugs
Great - That what its there for.
Hope you are treating it as a learning experience and enjoying.
 
I thought that asembler code was supposed to be completely unintelligble and
unsupportable and here you are finding bugs n thje code in a coupe of hours.
Well DONE
 
You have found several "Features" in the logic which I guess we are going to
have to change
 
But if we are going to fix them we are going to have be organized
 
First bugs/features that kill the system have to be fixed and then bugs that
are just annoying
 
The good new is that when you deleted all the lines you had a Program Check
and the system threw you out but recovered.
 
1) We have an issues with Insert when there are zero lines
2) I have an issue deleteing all the lines usng DD DD
3  Translate table issues
4) any thing else?
 
Those all have to be fixed but not are critical for today - they do not kill
the app,
 
As far as routnes that are missing or should come
----------------------------------------------------------------------------
-----------
We need a change routine
And a HEX/DISPLAY edit routine
 
I would love to write them in "C" so that we could get over that hurdle.
But it all comes down to what we need and how fast we need it.
 
 
 
 
 
 


  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of
Mike Stramba
Sent: Friday, August 06, 2010 04:32 
To: [email protected]
Subject: Re: [H390-VM] Re: Fullscreen application Specs


  

Roc,

The bug is that *lower case* j, k, l are being erased / replaced
by blanks when CAPS OFF is in effect.

The "{ }" bug looks like it's because there are x40''s in the C0, D0
positon in the DSPLYCHR table in GEDIT ASSEMBLE.

Haven't figured out why the j,k,l (X'91 X'92 X'93 are getting
blanked out .. their entries in DSPLYCHR look ok.

Mike

On 8/5/10, Mike Stramba <[email protected]
<mailto:mikestramba%40gmail.com> > wrote:
> Roc,
>
> A couple bugs :
>
> 1) "C" files -
>
> -a) The editor seems to stripping out "{" and "}" characters
>
> -b) It's doing something weird with "#" characters, looks like it's
> seeing that character and then transforming the rest of the line somehow
>
> e.g.
>
> I open ABS C (on Brexx A disk)
>
> It's displaying:
>
> #inc.ude <math.h>
>
> So it's replacing the 5th character with a space (sometimes it seems
> to replacing it with a "." (period).
>