1. incbm.e : suggestion
Hi all,
i've tasted nice routine called 'incbm.e' by G. Bruke for converting bitmap
into 'text' .e file.
here goes my random suggestions as:
1) The option of excluding(omitting) palette info (including image only)
could be added into routine to reduce the size of generated .e file?
2) Similar routine for converting execution file (e.g. small .com file
like simple screen saver) into 'text' .e file could be developed?
Bye! from Lee woo seob.
2. Re: incbm.e : suggestion
At 11:16 4/02/98 +0900, Lee woo seob wrote:
>Hi all,
>
>i've tasted nice routine called 'incbm.e' by G. Bruke for converting bitmap
>into 'text' .e file.
>here goes my random suggestions as:
>
>1) The option of excluding(omitting) palette info (including image only)
>could be added into routine to reduce the size of generated .e file?
>
>2) Similar routine for converting execution file (e.g. small .com file
>like simple screen saver) into 'text' .e file could be developed?
I wanted the incbm release to be easily accessable so I put it into the
standard read_bitmap() format.
I have been using the method to save non-image data for a while and all of
my stuff uses the standard palette anyway so I hadn't been including the
palette.
I'll work on it tonight and post a version with a couple more options shortly.
Graeme.
3. Re: incbm.e : suggestion
At 11:16 4/02/98 +0900, Lee woo seob wrote:
>1) The option of excluding(omitting) palette info (including image only)
>could be added into routine to reduce the size of generated .e file?
>
>2) Similar routine for converting execution file (e.g. small .com file
>like simple screen saver) into 'text' .e file could be developed?
O.K. done that. I just posted it to Rob. It should be on the RDS page shortly.
It handles 1D sequences and 2D sequences that are 'rectangular' i.e. where all
level 2 sequences are the same length (as per a bitmap). In both cases the
sequences must contain only 8-bit integers.
Graeme.
4. Re: incbm.e : suggestion
Hi Graeme,
Thank you for updating your incbm.e. i've downloaded your new version
yesterday, and found it works well except 'incseq'.
it seems a mistypo exists in 'incseq'. In your code i found:
name=input("Enter a name for the....") -- in function 'incseq'
it caused 'type mismatch' error, since the 'input' takes only one integer
as it's argument. However, i think, it can be cured easily by myself.
Thanks again!, i think incbm.e is very handy util. for me.
Bye!
5. Re: incbm.e : suggestion
>it seems a mistypo exists in 'incseq'. In your code i found:
>name=input("Enter a name for the....") -- in function 'incseq'
Oops. Sorry about that. It's a lazy version of the old basic
routine that I use to plug values when I'm testing things. I
forgot to take it out.
try ;
puts(1,"Enter a ...")
name=gets(0)
name=name[1..length(name)-1]
Graeme.
