Thanks to ZenerDiode (would that be the 5.6 volt variety?). I knew that the iPAQ would work with both cards inserted as my old iPAQ did (HP2210 or something like that).
I have just written my first program on the device itself, and the good news is that the OpenDialog in BASIC4PPC will bring up files stored on CF card, SD card
and the Hard Disk if these are fitted. So maybe the Help could be amended to make this clear in due course. I find it handy to click the header of the rightmost "Location" column, as this will then list the files in bunches according to where they are. Incidentally, there are no icons representing these locations, just the text. There are icons for filetypes only. Are you thinking of File Explorer, which does show icons?
In response to Ariel,
How do you plan to implement the allocation of meaningful filenames
the short answer is that the meaningful filename is made up of a combination of an incrementing number plus a short description of the subject. The same name will not re-occur in the same folder. Now here is the long answer...
It is based on a system I have used for labelling and paper-listing my photos for 48 years now, which translated itself very neatly to both the disk folder system, file naming conventions and electronic listing in a spreadsheet or database. Yes, I said 48 years - learning a new computer language does not come as easily to me now as it used to, so I hope forum members will be patient with me!
First, you have to bear in mind that the vast majority of the photos are of aircraft, and aircraft have what amounts to a unique identifier painted on them - the serial or registration. So allocating a phrase as the "subject" of the photo is a no-brainer, it's the registration number - I shall use "HB-JHC" as an example, since I mentioned that one in an earlier post (it's a Swissair Airbus A330). I used to take each 35mm film as an entity, and the photos would be given a sticky label and ID in the paper list as follows: 88-03-05 (HB-JHC). That means the fifth shot on the 3rd film taken in 1988. When translated to an electronic database it became a UID field of 880305 and a Subject field of HB-JHC. Since 2000 the year element has become YYYY rather than YY. When translated to the computer folder system it became file "05 (HB-JHC).jpg" in folder "03" of folder "1988". You will see that simple string manipulation enables one to create the two database fields from the filename, or vice versa.
With digital photography the film number is replaced by a session number - usually a visit to a particular location on a particular date - and the shot number has become three digits.
To assist me when looking through my folders for a particular set of photos I have found it helpful to re-name them Session + date + location, for example "My Pictures/2005/12 23-03-2005 San Francisco", but that is just cosmetic. However, the location can be created programatically from database entries including the location, while the date can come either from the database or direct from the jpg EXIF data (if there is no BASIC4PPC library for dealing with jpg metadata, hopefully someone is working on it).
So, we have:
Main folder: "2009"
Sub-folder: "06 09-09-2009 Heathrow"
Files:
"001 (HB-JHC).jpg
002 (4X-ELD).jpg
003 (HB-JHC).jpg
..."
Note how you can take more than one photo of the same subject and still have a unique filename. I have yet to go beyond 999 shots in a single day, I shall have to re-think if I ever do!
This system, or a simpler one, can be used for general photography, so long as the user can think of a reasonably short and meaningful word or phrase to enter into the database subject field - and of course it must not contain any "illegal" characters (these should be identified by error-checking at the time of data entry). I do occasionally take photographs of other subjects, like my grandchildren, and their names work fine as the "subject" field and as the bracketed part of the filename.
Turning to the database side of things, this can record further details such as the operator of the aircraft, the type, and various notes. Some information can be imported from links to other tables. If the UID in the database is constructed from the filepath (eg 200903036 without the text part in brackets) it becomes reasonably simple to open the jpg by clicking on the entry in the table, constructing the actual path and filename on the fly, and very easy to find the image manually - but that is all desktop stuff as far as I am concerned. The key role of the PPC in my scenario is to allow temporary storage of CF card images on another medium. The file-renaming during the transfer would be a bonus, but can't be done unless the subjects have been noted in the database first - there may not be time for that until I get home.
Another possible function of my application would be to tag the jpgs themselves with information from the database, so that metadata library wouldneed to read
and write to the files.
I hope that explains everything. I need to get the basic file transfer program running by mid-November, for a two-week trip.
It has just struck me that the file-name allocation process could just as well be left until the images are transferred from the USB stick to my desktop (or actually to a 1 Tb USB drive attached to my desktop). It does not need to happen earlier. But either way, the logic will be just the same and it beats re-naming every jpg file one at a time manually.
Thanks for listening. Sorry the explanation was so long, but you did ask!
Caravelle.