• Andrew Hodgkinson's avatar
    As warned in the last log, pretty much all event codes and component IDs have... · e6b771f8
    Andrew Hodgkinson authored
    As warned in the last log, pretty much all event codes and component IDs have now changed along with many of the names, to provide a consistent name and numberspace for events and components. This also minimises number clashes (e.g. as was, the Save File origin when opened from a
    
    Hotlist menu with an already-used component ID). To get full details on
    this, please carefully read through TBEvents.h.
    
    Res files, Sprites files and Messages files have been updated again both
    due to the above, and routine additions (e.g. message support for a few
    Hotlist bits and pieces). !Run[D] files updated for FTP 0.11 and
    HTTP 0.36.
    
    In the Makefile, the Customer objects list was missing Save - must have
    moved something when I should've copied it, when adding in SaveFile or
    SaveObject in all probability. Now fixed. Couple of other bits and bobs
    fixed in the build environment (e.g. stuff saying !Argo instead of
    !Customer). Oh, and I've altered the MakeFile copy options again to the
    best compromise I can come up with. Newer is turned on for everything
    except !Run[D] and !RunImage, since both of those change between debug
    builds - otherwise if you'd built debug and non-debug versions, it was
    not possible to switch between them - one version would have the newer
    timestamp and thus never get overwritten.
    
    The default hotlist has had a few items added - that'll be about the end
    of it, I think; there's more than enough stuff in there now.
    
    Saving of the hotlist from the document menu and of URI files,
    directories and selections from the hotlist menu tree is now implemented
    - this new save system rocks... Oh, and you can save all images and
    backgrounds as sprites.
    
    Saving of items with Shift+Click to other applications directly now
    works, and is robust. Unique Scrap filenames are used, with data load
    bounces (e.g. if some pra - er, person quits the app they're sending
    to) working correctly - that is, give an error, keep the file, rename
    it to something safe, and open the directory it lies in. As opposed
    to normal app-to-app bounces, where the scrap file is deleted (see
    PRM 3-254). This means you can now look at README files in FTP
    sites, say, without using a disc intermediate. Or you can send pictures
    straight to ChangeFSI, fetch HTML links into editors, and so-on, and
    so-on - it's all very funky. Known problems include the ambiguous
    'invalid component ID' instead of 'file open' for *normal* (straight to
    disc) shift+click saves, and I think I'll introduce a unique name
    guarantee of some sort to stop 'file open' in the first place. Odd
    that the really tricky part (app-to-app) should be least likely to
    suffer from this!
    e6b771f8
!RunD,feb 3.5 KB