@ericb59
Since recompiling of library with float may increase size of com file I've decided to implement ftoa function in my code instead. That solved use cases I care about.
Thanks
Hello!
I tried to compile an example printTextGraphic.c in Fusion-c library and found a mistake in line 70:
CopyRamToVram(start_adr,&buff, 2048);
Obviously should be
CopyRamToVram(&buff, start_adr, 2048);
thank you for pointing this mistake Arsenlikum
Can you add me to your private development repository, @ericb59? My github account is in my user profile (it's the public email address).
As an incentive, I present to you this little experiment I wrote to learn how to use the V9990. I made it using the g9klib included in Fusion-C. And some temporary sprites I got from Air Buster.
And this video of the experiment.
Nice.
I hope you will continue on this way
I have some cleaning and updating to do on my GitHub before adding you...
I come back to you as soon as possible.
Am I correct in my observation that Fusion only uses the FCB and not FIB? I ask this because the example code has a block where the filename is fixed from 11 characters (filename extension without dot) to 12 characters filename.ext. When using FIB, there is no need for that. Adding FIB saves a few bytes because the OS (if MSX-DOS2) already has the code.
it use only FCB.
I do not know, what is FIB ?
FIB is the MSX-DOS 2 file handler data structure (FIB = File Info Block).
It is the structure used by most of the MSX-DOS 2 specific routines.
See: http://map.grauw.nl/resources/dos2_environment.php#c3_4
File Information Block is the MSX-DOS 2 version of the FCB.
Information here
and
more information
MSX-DOS2 supports FCB and FIB, so the developer has the choice: do I use MSX-DOS2 or do I choose MSX-DOS1 compatibility.