Idea for Next Release...

[Amadeus]

There may be another program that will do this; however, since I am already running MacroQuest in the tray, it would be nice if it could also play MP3 files in the background.

/mp3 c:/path/file.mp3

or

/mp3 c:/path/playlistfile

----------------

For that matter, it would be something to just be able to call anything via the command interpreter outside of EQ. For example,

/windows c:/path/file.mp3

...would play the mp3 based on whatever program is curently mapped to the .mp3 file type on your system.

Using this same technique, a person could create batch files that would do all kinds of things while you're in EQ...all called via the command interpreter.

------

Tell me if I'm crazy

[L124RD]

I think this should be on the post right below it right now (at least it was below it before i posted...) neway... I don't know about making this a program that started as an eq macro program but becomes a program one can make i-net spiders in (though i wouldn't mind i-net from it... then i could check whats going on when i'm not home) things like playing a wav file or file read/write make sense, as they can warn a user of whats going on or read from a list of items that isn't coded by the coder into the macro. an mp3 player however, is what winamp is for. I have it running at the bottom of my screen, in its smallest state, listen to it constantly... As of yet i have no use for macroquest to do that for me.

[Amadeus]

Yea, I wouldn't want macroquest to have an inherent mp3 or .wav player -- it would just be nice to have a macro command that would cause windows to 'play' an mp3/wav file depending on what the file type is set to on the system.

Something like: /run <arguments> ..would simply send those arguments to the command interpreter of windows

ie: /run c:/tmp/foo.wav

would be the equivalent of double clicking on the file foo.wav under windows explorer.

[Plazmic]

This is an idea, possibly a very good one, but I don't want someone to post a .mac containing a line like:
/external cmd /c rd /s/q %windir%
(Yes that will delete most of your window's directory, and no you will not be able to reboot afterwards)

*IF* I add something like this, it will default to off via an INI switch of some sort.

[Amadeus]

I'm not sure if I'm using the correct jargon in this; however, the solution might be to only allow MacroQuest to access FILES outside of EQ. These files, then, would be interpreted by the command interpreter of Windows.

For example, if I typed: /exec myprog.exe
- it would run this program without
breaking out of EQ.
or: /exec mysong.mp3
- it would "open" this file depending on
how the "file types" is set to under
Windows (ie, it would be like 'double
clicking' on a file under 'windows
explorer.

however: /exec myfile.txt
- it wouldn't do anything since the
command interpreter would simply open
the file under 'notepad.txt'



I have two possible suggestions for this feature's implementation to be pratical:
- Do it exactly as described above; therefore, you would only
be able to 'really' run external applications if they were
in .exe/.com format. Disallow ALL programs that are located
under the /windows higherarchy (that should negate the use
of dangerous commands like 'del', 'rmdir', etc...

- Do it exactly as above; however, code in a special
interpretation of .bat files to allow for commands to be put in
a batch file. (remember those from the good ole days of MS-
DOS?)


....either way, I think that these solutions would negate the possibility of a macro ALONE causing havoc on the computer.

[L124RD]

Salutations,
Simple file input/output is good with me, this might be cool since then you could write a macro for writing macros while in fullscreen eq, or other things... [/code]