RunCommand

[Brian]

Moshi, could you try this version?

RunCommand - Beta_0.0.0.3b.rmskin

This version completely eliminates OutputType=Auto since there is no real way to detect if a string is UTF-8 encoded or not. So instead of auto detecting, this version requires an OutputType. Options include: ANSI, UTF8 and UTF16 (which used to be the "Unicode" option). UTF16 is the default since the default program is still "%ComSpec%" /U /C. The encoding of the OutputFile will correlate to the OutputType.

Also, I re-ordered some of the code to capture the output quicker in hopes of fixing the problem no output capture.

-Brian

[moshi]

This version completely eliminates OutputType=Auto since there is no real way to detect if a string is UTF-8 encoded or not. So instead of auto detecting, this version requires an OutputType. Options include: ANSI, UTF8 and UTF16 (which used to be the "Unicode" option). UTF16 is the default since the default program is still "%ComSpec%" /U /C. The encoding of the OutputFile will correlate to the OutputType.

congrats! works just like it should.
i see the UTF-8 OutputFile is now encoded as "UTF-8 with BOM". so there is this control character in front. WebParser can handle this just fine. i have no idea whether Lua can deal with such files.
one thing for the distant future: recently i discovered that at least for me, that i like using the Quote plugin for local files as it is faster than the Webparser plugin. i am aware that it does not support UTF-8 of any kind. not really necessary but maybe worth a thought.

Also, I re-ordered some of the code to capture the output quicker in hopes of fixing the problem no output capture.

not sure about this one. it seems a little worse than before.

[jsmorley]

FYI, Lua is fine with the BOM.

[moshi]

is it possible to pass multiple parameters containing spaces to a batch file?
what works on the command line is:

Code: Select all

mail.bat "FirstName LastName" sender@gmail.com password recipient@example.com "This is the subject" "This is the body"

i tried multiple variations of quotes with the Parameter option, but they all seem to fail.

maybe something like this would be nice:

Code: Select all

Program=mail.bat
Parameter=""FirstName LastName""
Parameter2=sender@gmail.com
Parameter3=password
Parameter4=recipient@example.com
Parameter5=""This is the subject""
Parameter6=""This is the body""

[Brian]

i tried multiple variations of quotes with the Parameter option, but they all seem to fail.

It should be possible. I would probably do it like this:

Code: Select all

Program=mail.bat
Parameter=""FirstName LastName" "sender@gmail.com" "password" "recipient@example.com" "This is the subject" "This is the body""

Notice that I did not double quote each parameter, just the beginning and end of the Parameter option itself.

To catch the spaces inside the parameters, you may need to edit your batch file. Normally you would have %1 to represent your parameter. You can add the "~" modifier to capture parameters with spaces. You may also need to add quotes around it as well. So %1 becomes "%~1".

Someone correct me if I am wrong as it has been a while since I have done anything like that.

-Brian

[moshi]

works like a charm! thanks

did not need to edit the batch file.
actually the tilde is needed to strip the quotes

mail.bat "FirstName LastName" sender@gmail.com ...

Code: Select all

echo From: %1 ^<%2^> >mail.txt

would become

Code: Select all

From: "FirstName LastName" <sender@gmail.com>

while i what i do is

Code: Select all

echo From: %~1 ^<%2^> >mail.txt

to get

Code: Select all

From: FirstName LastName <sender@gmail.com>

[Brian]

Version 0.0.1.0 (Beta) is now available here: http://rainmeter.net/forum/viewtopic.php?p=92974#p92974

did not need to edit the batch file.
actually the tilde is needed to strip the quotes

Yeah, you are right. Its been too long since I have programmed batch files...

And thanks for all the testing. I really appreciate it!

-Brian

[moshi]

no problem at all. i like this plugin a lot, as it makes many things easier.
using a plugin and displaying the measure is a concept even a monkey can understand, while doing the same with several scripts and reading a redirected text output takes a lot more steps.

and i already have this skin (and a few calendars) here:

SphynxMailer.jpg

works great. but it is a little scary how easy it would be to steal other people's account details.

i am just not sure whether to upload it or not. will this plugin become a part of the standard Rainmeter install? or would, if i would include the plugin, the included one overwrite an eventually already installed newer version of the plugin?

[Brian]

will this plugin become a part of the standard Rainmeter install?

We don't have any concrete plans to add this plugin as part of the Rainmeter install at this time. jsmorley, poiru and I talked about it briefly almost 2 months ago and concluded that it might be best to release it separately for now to judge its use by others (especially from countries outside the US).

if i would include the plugin, the included one overwrite an eventually already installed newer version of the plugin?

If the plugin does make it into the standard Rainmeter installation, then that is the plugin that will always be used (no matter if a separate "3rd-party" plugin gets installed). Rainmeter always uses the plugins in the "Program Files\Plugins" folder over any 3rd party plugins located in the "%AppData%\Rainmeter\Plugins" folder (even if it is the same plugin, but a different version).

If the plugin does not make it into the standard Rainmeter installation, then the plugin could get overwritten when someone installs an "older" version of the plugin. Of course the user can tell Rainmeter to not install a plugin when installing a .rmskin (they would need to uncheck the plugin checkbox) - but I doubt a regular user ever does that (or even knows about it).

i am just not sure whether to upload it or not.

This is totally up to you. Since the plugin is still a "beta", you may want to wait until a final version is done (which I think will be soon!).

-Brian

[moshi]

If the plugin does not make it into the standard Rainmeter installation, then the plugin could get overwritten when someone installs an "older" version of the plugin. Of course the user can tell Rainmeter to not install a plugin when installing a .rmskin (they would need to uncheck the plugin checkbox) - but I doubt a regular user ever does that (or even knows about it).

yeah, that's a bad situation. can hardly be solved nicely with 32 and 64 bit versions.

my biggest problem with it right now is that i can not use the value of a measure with a FinishAction.

With the Webparser plugin i can do things like:

Code: Select all

[MeasureEvi]
Measure=Plugin
Plugin=Plugins\WebParser.dll
...
FinishAction=["someapplication.exe" "[MeasureEvi]"]

would be cool if RunCommand could do the same.

an OnChangeAction wont help in the scenario i have in mind, as the value (success or error) might not change, but still something new has happened.