home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!acorn!jbye
- From: jbye@acorn.co.uk (James)
- Newsgroups: comp.sys.acorn.tech
- Subject: Re: RISCOSlib questions
- Message-ID: <17270@acorn.co.uk>
- Date: 27 Jul 92 07:38:16 GMT
- References: <1992Jul26.171110.1@vxdesy.desy.de>
- Sender: jbye@acorn.co.uk
- Organization: Acorn Computers Ltd, Cambridge, England
- Lines: 26
-
- In article <1992Jul26.171110.1@vxdesy.desy.de> burke@vxdesy.desy.de writes:
-
- > [intro deleted]
- >
- >1) When should I call xfersend_clearunknowns() (or is it done by saveas?)
- >
- >2) Is it OK to just call wimpt_checkmode() on mode-change events; also, do
- > I have to call it during initialisation?
- >
-
- Hopefully I can answer your questions :-
-
- 1) The unknown_event handlers used by xferesend (saveas does very little and
- calls xfersend) maybe be left hanging around if the save has failed. Hence,
- you should construct your code as follows :-
-
- saveas(0xFFF,"TextFile",1024,save_proc,ram_proc,print_proc,handle);
- xfersend_clearunknowns();
-
- It maybe wise to always call clearunknowns as I beleive it won't give you
- any problems even is xfersend has stopped claiming.
-
- 2) You should call wimpt_checkmode() when you initialise and when you
- receive a mode change event.
-
- --James
-