ftp.wwiv.com/ftp.wwiv.com.zip/ftp.wwiv.com/pub/MISC/PBAPI10.ZIP/WHATSNEW.DOC

Text File | 1998-02-21 | 12KB | 245 lines

02/21/98 - Version 1.0 Release for PowerBasic v3.5

           Recompiled all Units to be compatible with PowerBasic v3.5

           Made corrections to the MNNNN Header Unit for the Read in
           message number from the SHORT INTEGER to LONG INTEGER value.
           "c" now represents Conference Numbers (1 to 9999). SHORT INTEGER
           "mn" now represents Message Numbers (1 to 999,999). LONG INTEGER
           "n" can either represent SHORT or LONG INTEGERs for the MNNNN
           Data Record Elements. Please read additional notes in the
           MNNNHDR.DOC located in the APIDOC.ZIP file.


05/20/97 - ßeta 1 - Release of the First Wide Beta of this API for the
           general public.

           Release of a limited Whoson.dat API Unit. Also released Screen &
           Menu API Units.

           Mouse API Unit was released as well, but I opted at this point
           not to document it as it is used mostly by other internal API
           Units such as Menu and Screen API Units.

           Created a template called DemoMenu.bas to help show how to
           setup commands from the Menu & Screen API Units.

           Added more functions and subs to the Util.pbu API Unit.

           Added four new sets of Functions to the Node.dat API Unit.
           These have to do with the Caller ID Services of TriBBS which
           I completely overlooked the first time around. These functions
           are listed below and have been documented in the nodedat.doc.

           Enable Caller ID:
             FUNCTION NODE_DAT_GetECIDF() AS INTEGER
             FUNCTION NODE_DAT_PutECIDF(n AS INTEGER)

           Bump No Info Calls:
             FUNCTION NODE_DAT_GetBNICF() AS INTEGER
             FUNCTION NODE_DAT_PutBNICF(n AS INTEGER)

           Bump Blocked Calls:
             FUNCTION NODE_DAT_GetBBCF() AS INTEGER
             FUNCTION NODE_DAT_PutBBCF(n AS INTEGER)

           Bump Out Of Area Calls:
             FUNCTION NODE_DAT_GetBOOACF() AS INTEGER
             FUNCTION NODE_DAT_PutBOOACF(n AS INTEGER)


        **************** Alpha Testing Doc's below ****************

04/21/97 - Release of the Events.dat API Unit

           The NODEDAT.PBU Unit had all of the "Put" statements not set
           correctly and would error out if you tried to change the data.
           FIXED!

04/16/97 - MNNNN_HDR_GetTU was not returning a trimmed string and stipping
           the CHR$(0) from the end. Fixed!

           The SYSDAT1.PBU Unit had all of the "Put" statements not set
           correctly.. This was my fault. All Put statements in the
           SYSDAT1.PBU now works. Fixed!

04/09/97 - Release of Node.dat API Unit

04/07/97 - Release of Sysdat1.dat and Sysdat2.dat API Units

           Cleaned up the PBAPI10.INC abit by setting the 10 Byte Sub
           structure as one Type Structure and then Dimentioning each main
           structure to share it among all Main Type Structures. This allowed
           me to quit declaring the 10 byte sub structure over and over for
           each Main Data Type that needed it, and helps cuts down on the
           size of PBAPI10.INC file as well.

03/25/97 - I reworked the PBAPI10.INC to now hold all of the Dimentions, and
           Declarations that I was still having everyone do in their programs,
           which pertained to the API.  Also, these were in the Demo 1 & 2,
           and all other sample bas programs.  I suppose I should have done
           this to make the API even more simpler to use right from the start,
           but I just didn't think about it.  Therefore, All DIM, LSET,
           VARPTR32, PUBLIC & POINTER Statements have been moved to the
           PBAPI10.INC File.

           In addition, the following include files will no longer be sent
           with this archive, and I highly recommend that you delete these
           from your directories as they are no longer needed or used.

           They are:
             ALIASIDX.INC, DOORTMP.INC, FAREA.INC, MCONF.INC, MNNNNHDR.INC
             MNNNNTXT.INC, NETWORK.INC, USERDAT.INC, USERIDX.INC, USERSPF.INC,
             USERSPM.INC, & UTIL.INC.

           It is very important that you keep the PBAPI10.INC and PBAPI10.PBL
           intact and use the complete set together as many Units call
           different Functions from other Units as External routines.

           What you will need to do in order to start a program with this new
           setup is add the follow 3 statements to your program and set to
           your path:

             $LINK "PBAPI10.PBL"
             $INCLUDE "PBAPI10.INC"
             TBNode1sMainDirectory = "C:\TRIBBS"


           The USERSSPM.PBU Unit had a bug in the USERS_SPM_PutLWMR function
           where it was not updating the infomation in memory. This has been
           corrected. Thanks David! :)

03/16/97 - Release of Users.dat, Users.idx, Alias.idx, Users.spm, & Users.spf
           API Units.

           Created a new sample program called DEMO2.BAS which will show you
           how the Users.dat, Users.idx, Alias.idx, Users.spm, and Users.spf
           work together to allow you to simulate logoning on to TriBBS. If
           you log in as a new user, then this demo will allow you to enter
           all needed information and then add you to all of the TriBBS system
           files. This DEMO will actually add a new user to your records, so
           either backup your users files, or just flag the dummy user for
           deletion when done. :) If you enter a user's name or alias that is
           already in the user records, then it will find the user and display
           a partial record to the screen.

           Created four new functions in the Util API Unit for input string
           contol. See Util.doc for futher details.

           Renamed Messread.bas to DEMO1.BAS.

           Had a minor bug in the Hashit(s AS AS STRING) function where it
           was leaving the entire 's' in upper case after it was done
           creating the hash value. Didn't catch it until I started inserting
           records into the Users.dat file and the Users Name was showing up
           in all Cap Letters.. This is now Fixed!

           Added a new function called InitialCaps(s AS STRING) AS STRING
           to the Util Unit. See Util.doc for details.

           Reworked the "Search Message Number" feature in the Messread.bas
           file when  you select "Your" messages and then wanted to enter a
           new Message Number for either a forward or backward message number,
           this was not working the way I had intended.

           Changed MNNNN_TXT_Read(n AS INTEGER) to MNNNN_TXT_Read() in the
           MNNNNHDR Unit as the Integer value was not needed.

           Went through all of the units and now have them check the 'n'
           values for anything less than 1. Where 'n' in most cases refer
           to the record numbers. If 'n' is passed a value less than 1, then
           the function will exit out without reading the record number.

           Change the following ClearIt functions in each of the API Units:

             MCONF_DAT_Clearit()    ->  MCONF_DAT_Clearit(n AS INTEGER)
             NETWORK_DAT_Clearit()  ->  NETWORK_DAT_Clearit(n AS INTEGER)
             MNNNN_HDR_Clearit()    ->  MNNNN_HDR_Clearit(n AS INTEGER)
             FAREA_DAT_Clearit()    ->  FAREA_DAT_Clearit(n AS INTEGER)

           The reason for the change was I was wiping out the entire data
           file when you called this function. This was not intended to
           operate like that.. Now when you call this function, you must
           open the data structure you want to work, then call the Clearit
           function for that unit and pass the record number in 'n' which you
           want to clear out. This is also useful for calling to add records
           to the end of a data structure. Let's say you have 300 users
           records in the USERS.DAT file and want to add another record. You
           would open this file, get your length or total records add one to
           it and pass it as 'n' to the function like so: USER_DAT_Clearit n.
           This would add a blank record number 301 ready to be filled in.

           All future new Units with the Clearit() function will operate in
           the same manner above.

02/19/97 - Release of Mnnnn.hdr & Mnnnn.txt API Units.

           Updated the Util unit and did the doc file on this as well.

           Created file called Messread.bas which uses many if the Units
           from the API together to show how to call multiple functions
           from different units. This little program will allow you to read
           messages directly from the TriBBS \mwork directory without having
           to log on to TriBBS. I believe I got most if not all bugs out of
           this example.. :) Also, I am not responible for any "Fuzzy Logic"
           due to many late nights of programming. <VBG>

02/08/97 - Release of Mconf.dat & Network.dat API Units.

           I was having problems between unit's when I opened multiple files
           with my Internal FREEFILE Function. This is has been corrected.

           I have rearranged some of the Public and External calls so you
           only need to put "PUBLIC TBNode1sMainDirectory" in your main
           program. Let me know how it works for you. It seems to run smoothly
           without have to declare other variables in my Public statements
           here. :) Just look at each example *.bas file I send with the
           unit's to see exactly what has to be Dimention and Declared for
           operation for each unit.

           Made some changes to all the sample *.bas files.. Take a look at
           each one.

02/06/97 - Rewrote some of the FAREA's Unit to be more inline with the newer
           function calls I am now using.. After completing the DOORTMP Unit,
           I was very happy with this outcome and wanted to make the rest of
           my Units with the same approach using this same format. Now the
           FAREA Unit makes calls in the same manner as the DOORTMP Unit.
           Only exception is, in the DOORTMP Unit, on any OPEN statements I
           have it check first for the Doors.tmp file to make sure it is
           there before tring to open it, other than that, both of these
           Units are the same, and future Units will have this same format.
           If anyone has a better idea, nows the time to tell me. :)

01/31/97 - Release of the Doors.tmp Unit.

           Renamed the previouse "sample.bas" for the file area to
           "farea.bas". I did this to allow me to make new sample
           programs for each new unit as I develop them. All sample *.bas
           files provided will now be named after the Unit that is in the
           Main Library PBAPI10.PBL.

           Set all Lib's to 'ON' in the Units I create now so it will
           support all video's, graphics, serial communications, printer,
           debug info, error tests, allow crtl break operations. You will
           have to turn these off in your main program if you don't desire
           to use these in your program design.

           Change the pointer name in FAREA's Unit from 's' to 'fa' to
           try to keep each Unit's pointer name different so if anyone
           opens multiple files and make pointer calls, I didn't want to
           worry about any conflicts in the pointers or their names. :)
           Therefore, each Unit will have their own pointer assignment name.

           I have added the DOSUNIT.PBU, DATEUNIT.PBU, & DIRUNIT.PBU from
           PowerBasic's Units to the this library so I can now start making
           certain calls for dos services from within my own Units.

           Now I will supply seperate *.INC files for each Unit's File
           Structures and Declarations and also a complete master of all
           File Structures and Declarations in a new file called PBAPI10.INC.
           Also, the Declarations for the DOSUNIT.PBU, DATEUNIT.PBU,
           & DIRUNIT.PBU have been added to the PBAPI10.INC file.