RISCOSlib questions

Thread View: comp.sys.acorn.tech

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by burke Sun, 26 Jul 1992 17:11

#79

Author: burke
Date: Sun, 26 Jul 1992 17:11

13 lines
1124 bytes

I'm currently writing my first RISCOS-lib application (and my first real
program in C for that matter); I must say that I haven't yet found it as
dreadful as some of the other comments suggest :-) Anyway, a couple of
questions:

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?

Stephen Burke                                 [C programmers do it in braces]

Is this the first post in c.s.a.t? There's nothing else visible here, anyway.

Re: RISCOSlib questions

#80

Author: James
Date: Mon, 27 Jul 1992 07:38

26 lines
1263 bytes

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

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads