1.23a
The program runs best on a RISC OS computer with OS 3.60 or higher.
It no longer works on 3.1x with slightly reduced functionality.
This version requires the 32-bit C library, and also uses the Repeat utility provided as part of the 'new' universal boot, so these will be needed for OS versions earlier than 3.5.
Also, certain features are only enabled in registered copies.
Apparently it will on a PC under Red Squirrel or Virtual Acorn.
It acts upon a chosen directory, selected by dragging the directory filer icon to the program window, containing appropriately-filetyped* JPEG images also having a '/jpg' or '/jpeg' extension and placed inside a sub-directory called 'gallery', and it creates a thumbnail index for these images.
Certain characteristics of the index are user-definable.
Images loaded by the index appear centred in their own browser page and can have a filename or a definable title or 'comment' below them. Sets of large images can be scaled, and the size of the thumbnails can be altered.
There are also optional navigation icons to step forward or backward through the images or to return to the thumbnail index page, or this may be performed by clicking on the image itself.
From version 1.20f, these JPEG images may be Exif files straight from the camera if you wish - appropriate thumbnails will be made OK. But note, if your OS version does not allow the plotting of Exif files natively, then the on-the-fly generated thumbnail will not be available in the comments editor.
The HTML files produced by Pic_Index should conform to the World Wide Web Consortium (W3C) standards for HTML 4.01 Transitional as generated and are marked as such in their headers.
This means that they are entitled to show the logo(s) as displayed on the Pic_Index home page, but users need to verify this for themselves, particularly if they have altered the contents of the messages files or added material of their own.
On loading, the application opens a window to the centre of the screen as shown. When the target directory containing a sub-directory 'gallery' containing the JPEGs to be indexed is dragged to the window its pathname appears in the dialogue box.
NB The case does matter! 'Gallery' will not do, as, although the program will appear to work OK and may work 'locally', the results will NOT work under UNIX via the WWW, as UNIX is case sensitive! Therefore the program will force the name to lower case.
There are also various options for layout and thumbnail image quality which may be chosen.
The index uses tables to display the thumbnails, and the number of columns, maximum width, and cell spacing can be set here.
Additionally, one can chose whether or not to use links, add names (filenames or comments), and to add borders to the page layout.
A recent feature allows comments, if present, to be substituted for filenames on the index page as well, and note that clicking with adjust cancels the radio icons, so you can have nothing.
The contents of the setting window are now reflected in a mimic in the main control window.
A page background may also be selected by cycling through a selection of tiles. Background textures may be added by the user to the selection available.
A page title for the index page may be entered here instead of a default. Any disallowed characters are converted to the corresponding glyph.
The quality and nature of the thumbnail JPEGs can be set in the following section of the main window.
The lower section allows navigation tools to be added to the image pages if required.
Their function is duplicated by a client-side image-mapping system on the image itself:
Clicking on the horizontally central portion of the image links back to the index page, the left links to the previous image in a set, and the right hand quarter to the next image.
This is explained in the Help link at the bottom of each page.
An additional option adds a link to the index page to an index page in the parent directory. You can choose from a pop-up menu if this has a file extension of .htm, .html, or .php to fit in with your circumstance/style. Additional extensions could be added by editing the Text/Menu file in Resources. This allows various albums of images to be accessed from a 'parent' index page which can be returned to via this link.
The final option turns on and off and allows customisation of a copyright message under the images on the index page.
An optional iconbar icon (programmable from the Messages file) will either bring an already open window to the front or open a fresh one if one is not already open.
A menu may be obtained over the window as below:
Registered copies will display the owner's name.
Only 20 profiles can be defined, and the Default cannot be over-written from within the program.
This allows the saving of thematic settings for later use under meaningful titles!
Note that the setting of the background colour will, if a background texture is in use, offer you a suitable background colour corresponding to the average or predominant colour of the texture.
Which is offered depends on the percentage of the dominant colour. The breakpoint is set initially at 75% in the messages file.
You may accept the value offered (which is best viewed in 32 thousand colours or more) or choose your own.
The background colour is not displayed by your browser, but is used by RISC OS to calculate data for anti-aliasing the text, so should be appropriately set.
When a directory has been processed, a Comments file is created in the target directory which, before editing, just lists the JPEG filenames without their extensions.
The file format is the comment, followed by a marker character (# as set by default in the messages file), followed by key-words relevant to the image up to 255 characters in all.
The thumbnail largest-dimension is also stored in the messages file, and is set at 100 pixels like the default thumbnail. The editor thumbnail is always plotted direct from the original to avoid problems with progressive thumbnails, and will be coloured as the original.
Whilst there is no built-in provision within the program for displaying the full-size image, if a viewer such as PrivateEye or SwiftJPEG (HippoSoft, and Iyonix compatible!) is loaded, clicking on the editor thumbnail will launch the image into it for closer examination when required. There is a link on the site links page.
Keyboard shortcuts: Tab and up/down arrows move between fields, Page Down & Page Up do next and previous image.
The purpose of this is to allow the filenames to be added to with, or substituted by, a title (comment) or other explanatory text relating to the image.
This last option also adds the files to make a self-contained RISC OS application if the directory name starts with a pling (!).
It is present to allow images to be added to a directory. If a comments file is already present, the application does not try to make a new one, so if you add pictures the comments file is now too short.
Therefore you should delete the comments file before adding any pictures to an existing gallery.
To avoid losing any existing comments completely, you can save your existing comments file elsewhere from your text editor. Then use Delete file before re-processing the enlarged gallery.
Once you understand the simple list format of the comments file, you will be able to edit and add to them directly from your editor. The only rule is that there must be at least one line present for each picture, otherwise an error will occur on reprocessing.
Here you can also set a scaling factor for displaying your images in the browser, and the maximum dimension of your thumbnails in pixels
The last entry on this sub-menu, On last image, gives some control over the navigation behaviour when the last image in an album is reached.
Processing of a target directory is usually done by clicking on the OK button, although Remake HTML will do all but the creation of the thumbnails.
Adjust/Click on the OK button will just Remake HTML.
This latter can save a lot of time when re-processing an 'album'.
The current version (1.08 and above) saves the choices inside the created album directory, and these will be reloaded on editing.
If the album already contains a thumbnail directory ('thumbs'), clicking OK with Select will bring up a query box offering you some options.
These are to Abandon (duplicated by the Escape key) in case you've clicked OK by mistake, None, which will just reprocess the HTML files etcetera without remaking any thumbnails (duplicated by SpaceBar), New, which will only make thumbnails for any not-previously thumbnailed images (duplicated by the N key), and All, which will process/reprocess all the thumbnails (the default action on pressing the Return key). Intelligent use of these options will save wasted time.
A gallery directory of 4 images inside an otherwise empty directory called Photos - contents of the gallery directory shown:-
The 'gallery' contains the original full size images.
This gives, on loading the file index/htm, a browser thumbnail index (shown here half-size) as follows:-
The file 'comments' initially contains a list of the filenames:-
The second image would then. for example, no longer appear described as 229f/jpg in its main window, but instead (here at half-size) as:-
Version 1.09 and later has a pane attached to the left-hand side of the main window which reflects certain items from the main window - the selected tile if any, whether a border is set for the thumbnail images, and whether Monochrome is set for the thumbnails or whether they are in colour. It also provides a means of setting the background colour and various other colours as shown in the menu below via the colour picker under RO3.5 and above.
This shows the structure for version 1.21:
The final menu item allows combinations to be saved as a Choices file which can later be reloaded by dragging to the main window at will. This allows a library of tried combinations to be kept.
The format of this file is presently as follows:
The setting of the background colour to visually match any tiling used allows RISC OS browsers to take full advantage of text sub-pixel anti-aliasing to improve the presentation of text beyond that of inferior systems.
A whole batch of files can now be processed in sequence (perhaps overnight!) using a simply-prepared script.
This script is a text file and contains three kinds of line.
The script name must start with 'batch', and its icon should be dragged to the main window.
Before processing starts any choices files are checked for version compatibility, and any albums are checked to make sure that they have a gallery directory. Then, if these are satisfactory, the program checks with you if you need to make the thumbnails or not, and then processing starts in the order of the script.
For example, in this script below:
Then, provided that it does not already have its own choices file within it, it processes the album 'France' using these settings.
The next line is ignored as it is not a valid path or a line beginning with a '#'.
The procedure is repeated with the choices file 'yellow', the title 'Test File of a Single Image', and the album '!test' (which, because it begins with a pling (!) will also have the necessary files added to make it an application album which can be run with a double-click!).
The final line will be ignored.
Note that the order is significant - if you put a title followed by a choices file, the title in the choices file would over-ride the one in the list!
Inside the Boot:Choices.Pic_Index directory, in a folder called textures, are the tessellating tiles to form the backgrounds as GIF, JPEG or PNG files. Each GIF or JPEG file has a corresponding sprite generated in a corresponding directory in the Pic_Index scrap directory.
If there is a discrepancy between the numbers of files within these directories, the sprites are regenerated using InterGif.
If any problems arise with textures or tools, deleting the Pic_Index scrap directory will force the sprites to be remade.
A simplified method of adding a texture by dragging a GIF, JPEG or PNG file to the tile icon in the main window has now been added, where the user will be offered the option to incorporate the texture. The file should not have a file extension and should be at least 35 pixels in each dimension!
Inside the Boot:Choices.Pic_Index directory, in a folder called tools, are numbered sub-directories containing the navigation tool sets available to Pic_Index. You can add your own tools in a sequentially named/numbered folder of your own. These should be GIF, JPEG or PNG files, and should have at least back, index, left and right components. Additionally, you can add a notes image for completeness.
If this latter is not present, a text alternative is used.
The files should be convertible to sprites by InterGif to provide the mimic icons for the main program window.
Additions will be available next time Pic_Index is run.
Pic_Index will now scale your main image by a scaling factor set in the Image Page sub-menu. This will be useful for high-resolution camera users.
Just for good measure, you can also set the thumbnail landscape 'width' - that is, the maximum thumbnail dimension in pixels - in the same place.
Using the scaling factor means that your JPEGs will still be as large as they were, but will display in the scaled size.
The disadvantage of this is that they will still take up loads of space, so for web use you would be better passing them through ChangeFSI first to actually reduce them, and then use a scaling factor of 1 in Pic_Index.
But it may be that, for example, when making a CD album or album set where space isn't at a premium, there is merit in keeping the high resolution photos available but just displaying them at a more suitable scale by letting the browser do the rescaling.
If you have mixed-size images which you wish to browser-scale to a fixed pixel size for the larger dimension, you can enter this in the lower option called 'max pixels' after selecting it. Otherwise the top option called multiplier will apply the same decimal-fraction factor reduction to each image.
As a rule of thumb, I find that I can get an album of from 16 to 24 images 640x480 pixels onto a single HD DOS floppy (1.44MB), depending on the content of the photos (the amount of detail affects compression).
A collection of 400 photographs of that size (a holiday in India) contained in 19 directories and batch-processed to give coloured thumbnails but no navigation tools started at 23.33MB and occupied 26.22MB after album creation.
The order in which images are displayed in the index file can be determined by editing the 'jpgs' file in the album. Of course, any corresponding 'comments' file must also be edited in similar fashion.
To stop Pic_Index overwriting this 'jpgs' file next time it is run, one must change the filetype of the 'jpgs' file to 'Text'. This is done from the filer menu obtained by clicking the Menu button whilst the pointer is over the 'jpgs' file icon in the filer window and entering 'Text' in the dialogue obtained from Set type.
This will prevent Pic_Index from altering it in future, and provide a visual cue that the image order has been modified from that dictated by the filer or image filing system in use.
A tip for ensuring that the 'comments' file corresponds to the 'jpgs' file if not using the internal comments editor is to overlap the two editor windows on your screen to give one-to-one correspondence between them.
It is worth noting that a similar effect can be achieved by using an image filing system and adding the JPEGs to the gallery in the order they are required to be displayed. The image filing system will ensure that they are processed in this order.
Alternatively, files can be renamed, perhaps with a leading numerical or alphabetical character, to ensure that they appear in the filer window in the desired order.
The comments editor, available only in the registered version, simplifies the adding of comments (text under the pictures) and keywords (used for the 'search' facility).
It displays a window where a thumbnail of the image, generated on the fly by the OS routines, is displayed with dialogue boxes for the comment and keywords. These are navigated using the arrows to move from image to image - or the Page Up and Page Down buttons, and the Tab and Arrow keys for the dialogue boxes.
Changes are not written back to the file until the OK button is clicked. Adjust will do an interim save. Cancel will prevent changes being saved.
It also has rotate arrows described in the next section.
If an image cannot be thumbnailed by the OS routines, a warning will be given and the image area left blank.
This might happen, for example, with a progressive JPEG and an OS earlier than 4.33.
The image could either be left as it is, or treated with Jclean.
Displayed thumbnails are linked to the actual image, so if you have a JPEG viewer such as David Thomas' PrivateEye or HippoSoft's SwiftJPEG (which is Iyonix-compatible!) booted or loaded, double-clicking on the thumbnail will load the full-size image for more detailed examination.
In a similar fashion, a button will send any 'extratxt' file associated with that picture to your default text editor for editing, or, if such a file does not yet exist, allow you to create it (see section on Notes and Extra Text).
This feature is available in the comments editor window. Two arrows above the navigation arrows allow rotation of the main gallery JPEG image, and this is reflected in the window.
This rotation is performed losslessly by the Independent JPEG Group's 'jpegtran' on-the-fly. How long it takes will depend, to some extent, on how much free memory you have available.
If the hourglass stays on for a long time, you probably are low on available memory.
Also, if you examine the rotated image in, for example, PrivateEye, it may appear to be barred. This is an artefact of RISC OS, and will not be apparent in the browser.
Note that the thumbnail image is now remade automagically when you rotate a gallery image. This is new in this version (1.21b).
Note also that whilst cancelling the comments editor window will not incorporate any changes you have made to the comments, any files you have rotated will remain rotated! A warning will be given.
Each created album has a linked cascading style sheet file called album/css to control the appearance of the pages. By default this is copied from the 'album' directory within Pic_Index, but if a similar file is present within the current user choices directory (found in Boot:Choices.Pic_Index.Profiles) this will be used instead.
With CSS aware browsers, this file can control various aspects of the displayed page. See, for example, the link CSS Properties for some basic information.
Copying the album/css file yourself into the user directories and editing it can give you automatic CSS control on a per-user basis.
If you don't want this flexibility, the global default will be used.
An extra directory called 'notes' may be placed inside an album in which may be placed a file related to an image. This will have a name corresponding to the name of the image without the /jpg extension. If this is a plain RISC OS filetyped text file, the program will ignore it, but it will be available in the album for future reference.
If the file is a text file having a /txt extension, then a link will be created on the image page below the image to this file. Thus clicking on this link will load the file as text into a browser for display in a separate window.
If the file is an HTML file with the file extension /htm, then it will create a similar link which will load the file into a separate window as an HTML page.
If the file is a URL file of type &b28 with no file extension, then the link contained within it will be used. This can be an absolute link or a relative link relative to the image's htxt file in the album.
Thus a notes file for an image "999/jpg" could be called "999", "999/txt", or "999/htm".
Additionally, from 1.20f, if a wave file is used, having an extension /wav and filetyped 'wave' (&fb1), this will also be recognised as such and your browser or a helper application may play it when the link is clicked.
The notes link will be the word 'Notes' unless changed in the messages file, where it's appearance may also be 'fine-tuned', or, if it is present in the selected tools set, an image called 'notes' will be used instead.
If a folder 'extratxt' is present within an album, the text of any image-corresponding files will be incorporated in the image page below the comment line. These should be just plain text files with no extension.
Thus an image "123/jpg" would cause the contents of "123" in the 'extratxt' directory to be added as the extra text if it were present.
It should be noted that the program makes no attempt to check the contents of these files for illegal characters, unlike the comments entry in the comments file, so care will be required to stick to plain ASCII seven-bit text. This has the advantage that valid HTML tags should be OK, though, for any special effects required.
Note that, as this is incorporated into the HTML file, each line should end with a <br> if followed by another. Even image tags can be incorporated to add extra items. I've used this feature to add "SOLD" signs to items in an art gallery display.
The extratxt folder is created automatically if required when an associated extratxt file is created from the comment editor window.
These features are handled by Pic_Index on an 'if there' basis, so need not concern the less-experienced user until they find that they need the feature.
If a directory containing albums is dragged to the main window, the option of making a master index page in that directory will be offered.
The directory dialogue box will indicate 'Make Master Index >'. Relevant options may be set in the main window/mimic pane such as page title, colours, background etcetera, and when OK is pressed a master index file 'index/htm' containing textual links will be created using the album titles as appearing on the album index pages and with the appropriate relative link.
The size and other properties of the unordered list of links in the body of the master index will be taken from the setting 'IND:' in the messages file rather than the standard body text size in the browser or CSS file.
If you wish to make multi-level structures with an index page in each level of albums you must start at the lowest hierarchical level. Pic_Index will recursively ignore any index files of albums already having an index file in the same directory as the album directories except in the top directory of the source. Thus it will not attempt to catalogue index files of albums already indexed - provided you start at the bottom level(s). Remember all albums should have a Back icon, as should all subsidiary indexes - that is, all but the master at the top level!
This facility will be particularly useful for large collections such as CD collections. As usual, the files produced are laid out with ease of further editing/customisation in mind.
Note that the master index will be created using the .htm extension, so you will need to have the extension for the Back icon setting set to this for your albums to make it work.
Available from the iconbar icon menu, or by adjust-clicking on the iconbar icon, Search opens a window to which a directory icon may be dragged from a filer window to search that directory. A key-word to be searched for is entered in a separate field, and on initiation, the directory will be searched recursively for comment files, which will in turn be searched for the key-word.
The data from this search will automatically be used to compile a vertical thumbnail directory using absolute pathnames of images which correspond to the key-word and giving the path and comment string.
When the thumbnail is clicked on, the full size image will be displayed.
To return to the thumbnail index, use the Back icon on your browser, as using the Pic_Index navigation tools will move you within that album.
The search result index is stored in the Pic_Index scrap directory, but a filer window to access it opens automatically when the search is complete. This file remains until you either replace it by a subsequent search, or delete it deliberately or by clearing the whole scrap directory. The filer window can be re-opened by clicking on the icon to the left of the key-word field. If this is greyed-out, there is no file present.
If you wish to search a root directory or an archive, you may Shift/drag an item from within the directory to the window, and just the directory path will be registered.
Options are included to allow searching of any notes files or extra text files present if this is required.
A statistics window is available which can be activated/de-activated via the iconbar icon. It can count albums for batch processing as well as images, and gives an overall timing. It is on by default, but this can be altered by editing the messages file.
The application will try to quit gracefully in case of error, but to deal with problems outside the direct control of the program, re-loading the program and offering the same "source" attempts to ensure that files relating to it have been closed. Please report any exceptions so that I may try to deal with them.
WARNING - non-standard JPEG files which are not understood by ChangeFSI will not be able to be used with Pic_Index. They will need pre-processing with another application such as Jclean or CleanJPEG (references on web site).
It may be as well to have a selective file-closing program to hand, as global file-closing can cause problems with other software.
Pic_Index uses the Scrap directory to store temporary files during its work. If Pic_Index fails to give you an error report gracefully, which is what it should do, and "crashes", then these temporary files will not be deleted as they would normally be, but will be left there. Looking at what is in them may help pinpoint the cause of a problem.
In the Pic_Index scrap folder will/may be found a folder called 'bits' which contains the background tile for the search results page, a file called 'CFSIlog' which records the commands sent to ChangeFSI for processing the images, a file called 'debug' which will be blank unless you have especially requested a diagnostic version, a file called 'Results', a folder called 'Result' which stores the HTML file which shows the result of a search, and two folders containing datafiles listing the currently available textures and tools, and their corresponding sprites used for display purposes in the Pic_Index windows.
The file 'Results' is used by both the Search routine and the Master Index routine to store data for compiling the HTML pages they each create.
All of these except the four folders/directories are deleted on successfully quitting the program.
The program is provided as a working version, but the most advanced features will not be available, and others will cease to work after a while, and it will be necessary to register to continue to use the program with these features. Registration conditions and method are available by e-mailing Enquiries@PicIndex.info and asking for them.
There are various further options which may be altered by editing the messages files. On machines with the old boot, these are within the application directory, but on new boot machines (Risc PC on, though RO4 has an intervening user directory) the current copy will be found in: !Boot.Choices.Pic_Index.profiles.<userprofilename> from where it may be loaded for editing.
There is now a separate messages file called 'global' for options applying across all users.
The one thing you may want to do is to alter the first part of the copyright message, but there are other things you can customise in there as well.
Make sure that you have a back-up copy of the file before you edit it, in case you make a mess of it!
There is an entry called "CED" now in the global messages file which contains a maximum value for the number of images in an album for the Comments Editor - this is needed so that space can be reserved to store the image information when the program starts up.
As supplied, this is set at 77 to conform to RISC OS 3 filer limitations, and will need increasing if you wish to edit comments for larger albums.
There is a special variable for users of HTMLEdit from RComp which will allow text to be inserted freely underneath the large images.
It is called "SCS" (for Special Comment String), which inserts an HTML comment having, instead of the %0 symbol, the pathname of a piece of text to be found in a directory called 'text' within the album directory.
The file has the same leafname as the image, but minus the file extension.
HTMLEdit can use this to substitute the piece of text for the HTML comment in the htxt files.
I'm documenting it here and have made it user-tweakable in case it can be adapted for any other software/purpose.
A similar feature is now to be found within Pic_Index where any textfile in a directory called 'extratxt' within the album will be incorporated as extra text below the comment if appropriately named. That is, the contents of a textfile called 333 in the 'extratxt' directory will appear as additional text below the comment on the 333/jpg image page.
This is added on an 'if there' basis.
The registered version of Pic_Index will run happily off a read-only medium.
To achieve this it stores information on your machine in two places:
It uses its own scrap directory to store temporary information, and Boot:Choices.Pic_Index to store more permanent information.
It is in Boot:Choices.Pic_Index that your registration file 'details' is stored along with a global messages file, folders for textures or tools, which is where any added ones will be stored along with those supplied, a file with hte current version number, and a folder called 'profiles' containing individual folders for each 'user'.
These folders contain a customised 'choices' file, a 'messages' files which could be edited for choices not available through the GUI, and possibly, if you wish, a bespoke 'album/css' file to control the appearance of album pages for the specific user. If that isn't present, the default will be used.
If you delete a user folder, the choices will be lost for that user, though the default will be recreated.
If you delete the textures or tools folders, any additions will be lost but the default set will be recreated.
If you delete your 'details' file, you will lose the extra facilities provided by registration - but I have a record of all registrations.
When Pic_Index is run, it checks the choices folder each time, replacing any default files.
It then creates sprites for use in the main window for textures and tools from the GIFs or JPEGs in choices and stores them in
When Pic_Index is processing images with CFSI, it logs information in a file called 'CFSIlog' there, and if in debug mode, other possibly useful diagnostic information in a file called 'debug'. De-bugging mode can be turned on by editing the Run file to set Pic_Index$debug yes by piping out the following Pic_Index$debug no temporarily. Exactly what is recorded here may vary from version-to-version.
In debug mode, Pic_Index will open the scrap directory automatically each time it is run.
If no errors occur, both these logging files are deleted when the program is quit. The textures and tools are left, though, to save having to recreate them next time.
Version numbering is by a number (eg, 1.20) and a letter suffix (eg, 'd'). The letter change signifies a version where the structure of the default profile file has not changed significantly, but other changes may have been made to, for example, the messages files for errors or menus. When such a version is applied as an upgrade, the program will happily use album choices from an earlier sub-version.
When the main number changes, all the files in <ChoicesWrite>.Pic_Index will be overwritten except for the registered user's details file, and album choices files will need to be remade for that version.
The program uses the DrWimp library to provide its multi-tasking and windowing capability, and a proportion of the registration fee will be sent to a charity by agreement with the current keeper/maintainer, Ray Favre.
ChangeFSI provides the image rescaling capability, JPEG quality and colour control.
Richard Murray has written the spravgpi utility especially for Pic_Index to allow it to offer a suitable background colour for a chosen texture, and the 32bit safe imgsize utility.
The progressive JPEG capability and file optimisation is added by jpegtrans from the Independent JPEG Group.
The idea came from an indexing program by Paul Vigay which is a plug-in to his AntUtils program, but which created its thumbnails on-the-fly by browser re-scaling and was thus, in my opinion, too slow for actual web use with slow connections.
The code to prevent more than one copy running was adapted from somewhere, and I would be pleased to acknowledge it if someone were able to tell me where it is from!
I am also indebted to Emmet Spier for his chkspr utility which he has made freely available and which I use in the RISC OS application indexes to make sure the spritefile matches the application name.
I acknowledge the kindness of the late John Alldred for providing his HTML tutorials and for allowing me to adapt his glyph translation code from Text2Html for use in this program.
Also the Musus Umbra, Adny Holdsworth for advice and code to try and avoid leaving open files in case of unforeseen disaster.
Thanks to Peter Hartley for InterGif used to provide the tool and texture sprites for the main window by converting the GIF files.
Thanks to Darren Salt for permission to distribute his png2spr utility within Pic_Index. This is used to provide the tool and texture sprites for the main window by converting the PNG files.
To Chris Terran for all his work with Exifs and for his advice and help freely given.
I am grateful to Colin L Sutton, Elma Alexander and Mark Rowan for their testing, bug-finding and considered advice, and to the many other users who have helped with suggestions and bug reports.
Contacts:
DrWimp - Andrew Ayre/Ray Favre - Home of books "Starting Basic" and "Dr Wimp's Surgery" and support of the Dr Wimp freeware package. Web site at: http://www.rayfavre.me.uk/drwimp.html
Richard Murray - Web site at: http://www.heyrick.co.uk/
Peter Hartley - InterGif - http://www.chaos.org.uk/~pdh/software/intergif.htm
Author - John Williams - johnrw@ukgateway.net
Program Web Site - http://www.PicIndex.info/
E-mail:
Enquiries@PicIndex.info
Versions
Acknowledgements
(unfortunately underscores are not allowed in web addresses!)