home *** CD-ROM | disk | FTP | other *** search
- File Box Module Release Note
- (Version 0.60)
-
- Loading
-
- This version of the FileBox module can be loaded (and the File Box task
- automatically started) by:
-
- - double-clicking on the FileBox relocatable module icon (in the Modules
- directory).
-
- - using the following command sequence in an Obey file (assuming FileBox is
- resident in the System:Modules directory):
-
- *RMEnsure FileBox 0.60 WimpTask RMRun System:Modules.FileBox
- *RMEnsure FileBox 0.60 Error You need File Box version 0.60 or later
-
- - double-clicking on the !FileBox application (which also performs other
- actions- see below).
-
- Desktop features
-
- The File Box Desktop task is RISC OS 3 friendly. It supports:
-
- - transparent sprite file dragging, based on the machines configuration
-
- - 2D-style or 3D-style windows, based on the system's configuration
- (although this can be overridden). The 3D style windows are compliant
- with Acorn's recommendations for the "new look", while the 2D style
- windows are derived from previous versions of FileBox windows.
-
- - interactive help (in conjunction with !Help application in the Apps
- directory)
-
- - outline fonts in dialogue boxes, as under RISC OS 3.5 and later
-
- To change your system's configuration option determining your preference
- between 2D-style and 3D-style windows, double-click on the !3DWindows
- application. This application toggles bit 0 of CMOS RAM byte number 140,
- which is used by RISC OS 3 friendly applications to determine the users
- preference for 2D-style or 3D-style windows.
-
- To change your system's configuration option determining your preference
- between transparent sprite dragging (using the RISC OS 3 DragASprite module)
- and rotating-dash drag boxes, double-click on the !DragASpr application.
- This application toggles bit 1 of CMOS RAM byte 28, which is used by RISC OS
- 3 friendly applications to determine the user's preference for the graphical
- representation of file dragging.
-
- New features since first public release
-
- Since version 0.50, a new SWI has been added which allows icons for
- extended filetypes to be correctly displayed in FileBox windows under
- FiletypeExtend. See the revised edition two (issue 2) manual for details.
-
- File Box application front end
-
- To initialize all File Box facilities, double-click on the !FileBox
- application. The !FileBox application provides:
-
- - A system variable <I> which is a synonym for the system variable
- <FileBox$GetInputFilename>
-
- - A system variable <O> which is a synonym for the system variable
- <FileBox$GetOutputFilename>
-
- - An alias command, *B, which alleviates a small bug which produces the
- error 'Not enough stack for filing system' or similar. This error occurs
- only with some commands, such as *IconSprites, when used in conjunction
- with the File Box system variables. If a command gives this error, prefix
- it with the *B command. For example:
-
- *B IconSprites <I>
-
- See also the Known bugs section.
-
- - A small arrow icon sprite which is used in the Load window. This is not
- essential to File Box, but does give the user a more positive indication
- of what is required when a Load window appears.
-
- TaskTypes utility
-
- The !TaskTypes application provides task window support commands, some of
- which make use File Box facilities. Please refer to the !Help file inside
- the application directory for further information.
-
- TaskTypes now uses FiletypeExtend so that the unregistered task types can be
- moved into the extended filetype space, and hence will no longer clash with
- other types in the 12-bit range. I thank Alan Glover (Acorn) for his offer
- to register the types in the 12-bit range (after Acorn initially rejected
- them in 1993), but to do so would violate Acorn's philosophy of "one data
- format, one editor, one type." The philosophy must change, not simply be
- overlooked.
-
- Known bugs
-
- I am aware of an elusive bug which has haunted the FileBox code variables
- since their development. I believe that the OS manual doesn't give full
- enough parameters for what a code variable is and is not allowed to do. I
- suspect the problem is a stack overflow or a corrupted register which causes
- nasty data aborts and the like. I will say that they used to work fine (on
- Edit on an A3000), but in recent times (running Zap on my RiscPC) they have
- failed to work consistently.
-
- At any rate, I am hereby advising users that the use of the code variables
- is deprecated, and may not be supported in future versions of FileBox. I am
- planning to write a command shell which fakes the processing of FileBox code
- variables, which will look essentially the same, but get things right where
- I suspect the OS goes wrong.
-
- Correspondence
-
- Any queries about this software, suggestions for improvement, bug reports or
- other requests pertaining to this software or its documentation are
- welcomed. The address to write to is:
-
- Kade Hansson
- Kasoft Software
- 4/73 Alexander Street
- Shearwater 7307
- AUSTRALIA
-
- Telephone (International): [61] 3 64287448
- Telephone (Australia): (03) 64287448
- e-mail: kade_fh@postoffice.utas.edu.au
-
- -
-
- Copyright © Kasoft Software 1997. All rights reserved.
-
- The relocatable module 'FileBox' was programmed by Kade Hansson. This module
- is suitable for use with all ARM-based computers running Acorn RISC OS
- version 3.10 or later.
-
- KASOFT and the Kasoft device are trademarks of Kasoft Software, and owned by
- Kade Hansson.
-
- ACORN is a trademark of Acorn Computers Limited.
-
- Published September 1997; Issue 1
- Written by Kade Hansson
- Published by Kasoft Typesetting
- Code KR09602,0601
-