BBC BASIC Programmers' Reference

User Tools

Site Tools

Trace: • changing_20the_20case_20of_20a_20string • uploading_20files_20to_20an_20ftp_20server • substituting_20characters_20in_20a_20string • using_20an_20atl_20container_20control • playing_20multiple_20wav_20files • getting_20the_20user_20idle_20time
reading_20and_20writing_20.ini_20data_20files

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
reading_20and_20writing_20.ini_20data_20files [2018/03/31 13:19] – external edit 127.0.0.1reading_20and_20writing_20.ini_20data_20files [2024/01/05 00:21] (current) – external edit 127.0.0.1
Line 2: Line 2:
  
 //by Richard Russell, May 2006//\\ \\  You may want your program to read configuration settings or user options on start up, to avoid the user having to enter them every time. One way of doing that is to use the //registry//, and this is described in the main help documentation [[http://www.bbcbasic.co.uk/bbcwin/manual/bbcwine.html#registry|here]].\\ \\  However there may be reasons why you prefer not to use the registry, for example you might like the configuration settings to be in a file which can be easily read and edited, and even transferred between different computers. In that case you can store the data in a **.INI** file, which is a text file in a standardised format. Here is an example of a .INI file:\\ \\  //by Richard Russell, May 2006//\\ \\  You may want your program to read configuration settings or user options on start up, to avoid the user having to enter them every time. One way of doing that is to use the //registry//, and this is described in the main help documentation [[http://www.bbcbasic.co.uk/bbcwin/manual/bbcwine.html#registry|here]].\\ \\  However there may be reasons why you prefer not to use the registry, for example you might like the configuration settings to be in a file which can be easily read and edited, and even transferred between different computers. In that case you can store the data in a **.INI** file, which is a text file in a standardised format. Here is an example of a .INI file:\\ \\ 
 +<code ini>
   [settings]   [settings]
   aspect=1   aspect=1
Line 15: Line 16:
   compressor=mp4v   compressor=mp4v
   quality=512   quality=512
 +</code>
 The file consists of a number of sections (here they are **settings** and **codec**) and within each section are one or more lines in the format "key=value". Windows makes it very easy to use such files because it provides API routines to access them.\\ \\  To read data from a .INI file you can use the following function:\\ \\  The file consists of a number of sections (here they are **settings** and **codec**) and within each section are one or more lines in the format "key=value". Windows makes it very easy to use such files because it provides API routines to access them.\\ \\  To read data from a .INI file you can use the following function:\\ \\ 
 +<code bb4w>
         DEF FNgetinistring(file$, section$, key$)         DEF FNgetinistring(file$, section$, key$)
         LOCAL buf%         LOCAL buf%
Line 21: Line 24:
         SYS "GetPrivateProfileString", section$, key$, "", buf%, 256, file$         SYS "GetPrivateProfileString", section$, key$, "", buf%, 256, file$
         = $$buf%         = $$buf%
 +</code>
 You would call that from your program in the following way, using the above file (called ARCQTM.INI) as an example:\\ \\  You would call that from your program in the following way, using the above file (called ARCQTM.INI) as an example:\\ \\ 
 +<code bb4w>
         aperture = VAL(FNgetinistring(@usr$+"ARCQTM.INI", "settings", "aperture"))         aperture = VAL(FNgetinistring(@usr$+"ARCQTM.INI", "settings", "aperture"))
         compressor$ = FNgetinistring(@usr$+"ARCQTM.INI", "codec", "compressor")         compressor$ = FNgetinistring(@usr$+"ARCQTM.INI", "codec", "compressor")
 +</code>
 Here it is assumed that the file resides in the user's **Documents** folder. You should always specify a full path to the file.\\ \\  Arguably, a better place to store the file would be the user's **Application Data** folder, which you can do as follows:\\  Here it is assumed that the file resides in the user's **Documents** folder. You should always specify a full path to the file.\\ \\  Arguably, a better place to store the file would be the user's **Application Data** folder, which you can do as follows:\\ 
 +<code bb4w>
         appdata$ = FNspecialfolder(26)         appdata$ = FNspecialfolder(26)
         aperture = VAL(FNgetinistring(appdata$+"ARCQTM.INI", "settings", "aperture"))         aperture = VAL(FNgetinistring(appdata$+"ARCQTM.INI", "settings", "aperture"))
         compressor$ = FNgetinistring(appdata$+"ARCQTM.INI", "codec", "compressor")         compressor$ = FNgetinistring(appdata$+"ARCQTM.INI", "codec", "compressor")
 +</code>
 The **FNspecialfolder** routine is listed in the main Help documentation [[http://www.bbcbasic.co.uk/bbcwin/manual/bbcwine.html#specialfolders|here]].\\ \\  The above examples retrieve the data as a string. If you know that the data will be an integer, then a simpler form can be used:\\ \\  The **FNspecialfolder** routine is listed in the main Help documentation [[http://www.bbcbasic.co.uk/bbcwin/manual/bbcwine.html#specialfolders|here]].\\ \\  The above examples retrieve the data as a string. If you know that the data will be an integer, then a simpler form can be used:\\ \\ 
 +<code bb4w>
         SYS "GetPrivateProfileInt", section$, key$, default%, file$ TO aperture%         SYS "GetPrivateProfileInt", section$, key$, default%, file$ TO aperture%
 +</code>
 The value **default%** is returned in the case where the section or key does not already exist in the .INI file, such as when first running a program. There is no equivalent system call for writing of integers and the method below should be used.\\ \\  To write data to (and if necessary create) a .INI file you can use the following procedure:\\ \\  The value **default%** is returned in the case where the section or key does not already exist in the .INI file, such as when first running a program. There is no equivalent system call for writing of integers and the method below should be used.\\ \\  To write data to (and if necessary create) a .INI file you can use the following procedure:\\ \\ 
 +<code bb4w>
         DEF PROCputinistring(file$, section$, key$, info$)         DEF PROCputinistring(file$, section$, key$, info$)
         LOCAL res%         LOCAL res%
Line 36: Line 47:
         IF res% = 0 ERROR 100, "Couldn't write to file "+file$         IF res% = 0 ERROR 100, "Couldn't write to file "+file$
         ENDPROC         ENDPROC
 +</code>
 You would call that from your program as follows:\\ \\  You would call that from your program as follows:\\ \\ 
 +<code bb4w>
         PROCputinistring(appdata$+"ARCQTM.INI", "settings", "aperture", STR$(aperture))         PROCputinistring(appdata$+"ARCQTM.INI", "settings", "aperture", STR$(aperture))
         PROCputinistring(appdata$+"ARCQTM.INI", "codec", "compressor", compressor$)         PROCputinistring(appdata$+"ARCQTM.INI", "codec", "compressor", compressor$)
 +</code>
reading_20and_20writing_20.ini_20data_20files.1522502376.txt.gz · Last modified: 2024/01/05 00:16 (external edit)