Simple Programming Challenge!Follow

I need a windowed program to run a timer. 1 hour duration, executing a chosen sound file every minute. At the end of the hour, another string to play a different sound.

Can anyone whip it up for me? This is the break down.

Load program
Click the start button
Every 60 seconds alarm.wav to be played
After 60 cycles, done.wav to be played.
Program stops.

It would mean more to me than you know, I'm tired of looking at a clock during power hour.

Oxymoron.

Twiztid

Everyone takes a 1.5 shot of "beer" on the minute for one hour. The steadiness is something else...

edit: GOT Em! Thanks a bizzillion kaolian! I'll try it out when I get home, thanks again.

Edited, Tue Jun 22 19:05:57 2004 by DeanoTyler

Yay, learned something new.



Attribute this to the rando-smash factor?

PS Please someone tell me how to source quotes

You know you're a nerd when you start using computer programs to facilitate drinking games.

Just do the power hour like everyone else. Use an analog wall clock, and after 45 minutes or so everyone gets too drunk to keep track, and it gets really sloppy.

eh, that works too, but mine is platform independant. Doesn't get much quicker or dirtier than an iframe, a few meta refresh tags and an embed tag or two. I could write it as a program and compile it under unix or windows, but why bother?

Just for the record, if you drink yourself to death using that, it's not my fault.

Who said he was worried? Compassion and covering one's *** are two different things, sonny.

Twiztid

I assume you mean the "DeanoTyler Wrote:" Thing.

Just do:
[quote=NameofQuotedPerson][/quote]

Huh? Of course they do. But their browsers don't support whatever funkyness you put on those webpages. When I click the links, the all say something like: "Viewing this page requires a plugin you do not have. If you'd like to download the plugin click here". Clicking the link there brings you to a page that says that the plugin you need is not found.

I did a bit of poking around. I actually think it's because the browsers are "new" instead of old. Older browsers used to have this feature where you could tell it manually which app to start up when it encountered a file of a particular type. I just noticed that the browser I'm using today has changed the way that's done. Now, everything is done via plugins. The only thing I can assume is that the plugin for audio/x-wave is not present by default.

Back in the old days, I could just add it in manually by referencing the type "audio/x-wave" to a binary on my local system (a wave player in this case). Can't do it now. Or at the very least, they've made it a lot harder to do then it used to be (I think I can add it in, but it would require a lot more goofing around with it).

It's kinda bizaare actually. I can do shockwave and flash and all that neato stuff, but can't just play a normal wav file. Go figure...


I've also noticed that that automated interaction with programs often don't work when using *nix (or macs in some cases) and accessing a file that was generated on a Windows based system. The cause ends up being the old "file extension versus file header" issue. Everyone in the world *except* microsoft embeds standard file headers into their stuff so that they know what sort of file something is. MS still uses the old concept of dos file extensions. What I've seen happen *alot* is that if you create a file of a particular type on a MS machine, it'll automatically stick a file extension on, but not put in a header. The result is that an MS machine will recognize it correctly (cause it's looking for the file extension) and do the right thing with the file. Any other platform will look at the file and have no idea what type it actually is and do nothing.


You see this all the time with .zip files. If the file was generated on a MS host, and I just click on the link, it'll open the binary in a window (which results in a lot of gibberish on the screen). The only way to get around it is to hold down the shift key while clicking. This tells the browser to just download whatever's on the other end of the link instead of the default behavior (opening in a window).


In this case, I don't think that's the issue since the browser does seem to know what kind of file is there. It just doesn't have anything configured to manage it by default. Which is strange, but then I didn't make the damn thing...