[Dialog] Where is the full scripting langurage reference?
Rocky
Where can one find the complete scripting reference for Dialog. The built
in help has only a small amount of information.
Thanks
Rocky
matija
> Where can one find the complete scripting reference for Dialog. The built
> in help has only a small amount of information.
nowhere, unfortunately. dialog's scripting is almost useless
at the time being. for example, i wanted to code a script that
would override dialog's onshutdown event and popup a message
box saying "close dialog: yes/no". i guess that's impossible...
--
there is a cheer. the gnomes have learned a new way to say hooray. [-shpongle]
address is scrambled - remove SPAMISEVIL to reply
Jernej Simončič
> Where can one find the complete scripting reference for Dialog. The built
> in help has only a small amount of information.
Dialog scripting is based on InnerFuse Pascal Script. It's author
recommends this book for information on syntax:
http://www.marcocantu.com/epascal/default.htm
--
Jernej Simončič, jernej....@guest.arnes.si
http://www2.arnes.si/~sopjsimo/
Bob Frank
> Rocky, completely geschtonkenflapped, wrote:
>> Where can one find the complete scripting reference for Dialog. The built
>> in help has only a small amount of information.
>
> nowhere, unfortunately. dialog's scripting is almost useless at the time
> being.
That seems awfully harsh. From what I've seen posted here it looks like
the scripting is extremely useful. It may not be easy for us
non-programmers, but that certainty doesn't mean that it's "almost
useless."
> for example, i wanted to code a script that would override dialog's
> onshutdown event and popup a message box saying "close dialog: yes/no". i
> guess that's impossible...
Just because you couldn't figure out how, or this is a feature not
supported by scripting, doesn't mean that scripting is "almost useless."
It seems to me that what you want to do would be outside the abilities of
any scripting language anyway.
Bob Frank
matija
>> dialog's scripting is almost useless at the time being.
>
> That seems awfully harsh. From what I've seen posted here it looks like
> the scripting is extremely useful. It may not be easy for us
> non-programmers, but that certainty doesn't mean that it's "almost
> useless."
1) it's a bit hard for non-programmers;
2) programmers don't have much to tweak.
yes, you can do _some_ things in dialog's scripting, but for
a lot you have to resort to external DLL calls and battle with
obscure and (bad) documentation from both dialog and microsoft.
thank god i have delphi with the RTL and VCL sources ... :)
that's exactly the reason i said it's almost useless - not many
examples in dialog, much less proper documentation and events.
>> for example, i wanted to code a script that would override dialog's
>> onshutdown event and popup a message box saying "close dialog: yes/no". i
>> guess that's impossible...
>
> Just because you couldn't figure out how, or this is a feature not
> supported by scripting, doesn't mean that scripting is "almost useless."
it just strikes me as odd that the onstartup/onshutdown events
are procedures instead of functions.
> It seems to me that what you want to do would be outside the abilities of
> any scripting language anyway.
not at all. all i need is "function OnShutDown : boolean;"
instead of "procedure OnShutdown;" and then i can have
---
program OnShutdown;
const MB_YESNO = 4;
IDYES = 6;
IDNO = 7;
function MessageBox(hWnd: longword; lpText, lpCaption: PChar; uType: longword): Integer; external 'Messa...@user32.dll stdcall';
function OnShutdown : boolean;
begin
if (MessageBox(null, 'Do you want to close Dialog?', 'Close Dialog', MB_YESNO) = IDYES)
then result := true
else result := false;
end;
begin
end.
---
right now all i can do is display a "thank you for using dialog"
message box and do the same when it's starting up. what else?
---
program OnXover;
procedure OnXover(Var XoverData:TXoverData);
begin
if (pos("sender name", XoverData.From) <> 0)
then XoverData.Score := 100;
end;
begin
end.
---
this piece of code is indeed useless because that same thing can
be accomplished by scoring. that and dialog's exposed options take
care of the rest of TXoverData members. the onbeforesendingmessage
event seems nice, but how the hell am i supposed to figure out
what "var Message: TStringlist" consists of? if it's just plain
text with plain headers and plain text content (i guess it is,
but who knows), one could add custom x-headers depending on the
group/sender you're replying to (or something). could be fun if
you picked on someone and every followup to that person's post
would have "x-john-doe: MAJOR TROLL!!!" added automatically or
the x-face changed :)
i'd also like to code a gravity-like VCR function: a dialog
box with the names of all newsgroups you're subscribed to.
you put checkboxes next to those for which you want to retrieve
headers and/or bodies, perhaps set up a timer, click "OK" and
have dialog get the things you want. well, i can't do that now
because i don't have access to the subscribed newsgroup list.
so, dialog's scripting is both useful and useless at the same
time. would we find middle ground on this issue if i just said
it's LIMITED at the time being? :)