Silverfrost Forums

Welcome to our forums

Change in the way BEEP@ works?

12 Dec 2016 11:34 #18540

I have been using the CALL BEEP@ to signal to the user that there are errors. If I call BEEP@ from my main window (uses %tx), I do not get a sound, but when I call BEEP@ from a special error window, then the sound is heard.

I am searching archives to find that last date at which the beep sound could be made.

13 Dec 2016 1:55 #18541

I stand corrected; the version of 13 July 2015 also has this beep missing feature (V7.20 of FTN95).

I know this is obscure, and I can get by without it, but it is something that seems to be out of the norm.

Bill

13 Dec 2016 2:52 #18542

Oops, never mind; found a sneak path around that section.

13 Dec 2016 3:17 #18546

Hi Bill,

BEEP@ has the advantage of being dead simple. I found that sound alerts sometimes annoy users, and I have a menu option to turn them off.

PLAY_SOUND_RESOURCE@ is a more sophisticated option that allows you to have a variety of different alerts, and there's also PLAY_SOUND@ which I've never used, plus a whole bunch of sound recording and playing routines. Maybe one of those helps.

Eddie

10 Dec 2022 6:15 #29688

As a matter of my usual Saturday Devilry day faults and problems - does play_sound_resource@ work with 64bit? Is this just with my case or it does not work at all? It was included the same way as for 32bit programs by adding word RESOURCES at the end of Fortran file and the reference on SOUND file.

Please login to reply.