Shoutbox

quote:

---

Originally posted by tryxter
Update system (the ability to automatically download the new plsc file, uninstall the current version, and install the new version)

---

No need for that tbh. Simply reinstall the new version, being it manually or being it with the previous script itself that doesn't matter. As a matter of fact, many scripts already do this...

quote:

---

Originally posted by tryxter
Being able to stop and restart scripts

---

as for restarting, see "CookieRevised's reply to Restart script through code".

quote:

---

Originally posted by Choli
One thing more to add to the scripting engine: The ability to call functions which return void. Currently, functions called with Interop.Call must return something. I'd like to call functions such OutputDebugString or Sleep which return nothing (void).

---

Already possible since there is no difference actually (PS: they return 0). And if you don't want to waste a variable which would contain nothing anyways, then call the function as a procedure... Works perfectly here.

eg:
// Do something here and suspend execution of Messenger for 5 seconds
Interop.Call("Kernel32", "Sleep", 5000);
// Print a debug Message
Interop.Call("Kernel32", "OutputDebugStringW", "Hello World");
// Continue whatever you were doing


http://www.microsoft.com/technet/sysinternals/Mis...ous/DebugView.mspx

I would like a function to grey out certain controls (eg. CheckBoxes) in PlusWnd objects

edit: and maybe even to make them (in)visible too...

Or a more VB-alike way of controlling the controls in a pluswnd, so that you can access and edit any property a control has through scripting.

Example: PlusWnd.ControlId.Property = value;

quote:

---

Originally posted by Eljay

quote:

---

Originally posted by Jesus
I would like a function to grey out certain controls (eg. CheckBoxes) in PlusWnd objects

---

If you mean to disable them, this should do the trick:

code:

---

Interop.Call("user32", "EnableWindow", PlusWnd.GetControlHandle("YourControl"), 0);

---

---

Actually it would be:
Enable:

code:

---

Interop.Call("user32", "EnableWindow", PlusWnd.GetControlHandle("YourControl"), true);

---

Disable:

code:

---

Interop.Call("user32", "EnableWindow", PlusWnd.GetControlHandle("YourControl"), false);

---

Because it's a BOOL over at MSDN

quote:

---

Originally posted by vikke
Actually it would be:
Enable:

code:

---

Interop.Call("user32", "EnableWindow", PlusWnd.GetControlHandle("YourControl"), true);

---

Disable:

code:

---

Interop.Call("user32", "EnableWindow", PlusWnd.GetControlHandle("YourControl"), false);

---

Because it's a BOOL over at MSDN

---

quote:

---

Originally posted by windef.h
#define FALSE    0
#define TRUE    1

---

lol I hadn't thought about Interop.Call yet, gonna try that now. Thanks for the tip.

Anyway I still want the VB-like way of editing properties like in the edit in my previous post...

quote:

---

Originally posted by Jesus
lol I hadn't thought about Interop.Call yet, gonna try that now. Thanks for the tip.

Anyway I still want the VB-like way of editing properties like in the edit in my previous post...

---

I guess I could make a script/library that allowed for that sort of thing, but it would be complex (especially as we can't extend the Plus default objects (in this case PlusWnd)).

quote:

---

Originally posted by Eljay
I guess I could make a script/library that allowed for that sort of thing, but it would be complex (especially as we can't extend the Plus default objects (in this case PlusWnd)).

---

would that make it just complex or impossible (for now)?

this is the thread for scripting API suggestions, so we could add "the possibility to extend Plus! default objects" to the list too (if it isn't already on the list, that is)

quote:

---

Originally posted by Jesus
would that make it just complex or impossible (for now)?

this is the thread for scripting API suggestions, so we could add "the possibility to extend Plus! default objects" to the list too (if it isn't already on the list, that is)

---

I think it's already on the list, it doesn't make it impossible to do, it just means it would need to be done differently. Although it's already hard enough to do because I would have to parse the XML myself to get the ControlId of each control and afaik they are not available anywhere else.

quote:

---

Originally posted by Eljay

quote:

---

Originally posted by vikke
Actually it would be:
Enable:

code:

---

Interop.Call("user32", "EnableWindow", PlusWnd.GetControlHandle("YourControl"), true);

---

Disable:

code:

---

Interop.Call("user32", "EnableWindow", PlusWnd.GetControlHandle("YourControl"), false);

---

Because it's a BOOL over at MSDN

---

quote:

---

Originally posted by windef.h
#define FALSE    0
#define TRUE    1

---

---

I know your code was working but it should be a bool

quote:

---

Originally posted by vikke
I know your code was working but it should be a bool

---

Actually it doesn't make a difference.

quote:

---

Originally posted by Script Docs > Interop.Call

If the parameter is a boolean, a number is sent: 1 for true, 0 for false.

---