Shoutbox

the only thing I'll say on this subject is: careful. Subclassing windows properly is something that takes time and anybody doing this kind of thing needs to make sure his code is tested extensively.

As for using GetCallbackPtr with SetWindowLong: don't. The documentation specifically mentions that this function can only be used for synchronous calls. If you make a script that defys this rule, it may work at first but the combination of several scripts will certainely cause unexpected results / crashes.

quote:

---

Originally posted by deAd

quote:

---

Originally posted by CookieRevised
Isn't the reason you want to subclass something because you need to catch just a certain message? I don't see why you would want to catch all possible messages there are, that would be useless (unless you make a Windows Message Spying program).

---

Yes, but you have to send the messages you don't want back to the original windowproc. You can't do this with a Plus! window because you only have control over the messages you ask for.

---

But aren't all other messages already forwarded to the original WinProc by Plus!?

Though I know this wouldn't work in all situations either though, and it is a bit of a dirty method. But I think this might be possible for specific things

EDIT: Plus! doesn't know the original WinProc, that would of course be the reason, no?

quote:

---

Originally posted by Patchou
As for using GetCallbackPtr with SetWindowLong: don't. The documentation specifically mentions that this function can only be used for synchronous calls. If you make a script that defys this rule, it may work at first but the combination of several scripts will certainely cause unexpected results / crashes.

---

I know this would be a lot to ask, but can you explain this in more detail and/or with an example, as I like to understand in much detail why it would cause a crash/unexpected results in some cases.

EDIT: apparently not possible Just had a quick chat with Patchou. In short:

quote:

---

Originally posted by Patchou
the problem is a technical limitation: for callbacks I dont have much other choice than using static functions in my code so I cant have two scripts using a callback at the same time, which is why they have to be synchronous.
...
Thus right now, calling GetCallbackPtr() many times, from different scripts, will always return the same pointer for a function with a given number of arguments.
...
Meaning two scripts can't subclass any two window at the same time. Even one single script wouldn't be able to subclass two windows with that method.
...

---

Now, he also gave a hint as in how it would be possible, but that involves asm (which _is_ possible in scripting, but extremely advanced).

quote:

---

Originally posted by CookieRevised
EDIT: Plus! doesn't know the original WinProc, that would of course be the reason, no?

---

Yes, this is the reason. Plus! would call the default Windows message handler and the chat window's message handler would never see the messages.

quote:

---

Originally posted by CookieRevised
Now, he also gave a hint as in how it would be possible, but that involves asm (which _is_ possible in scripting, but extremely advanced).

---

It's very messy, but you can inject the ASM bytes of a new wndproc into memory and use a pointer to those. It's really better to just use a dll if you need to subclass.

quote:

---

Originally posted by deAd

quote:

---

Originally posted by CookieRevised
Now, he also gave a hint as in how it would be possible, but that involves asm (which _is_ possible in scripting, but extremely advanced).

---

It's very messy, but you can inject the ASM bytes of a new wndproc into memory and use a pointer to those. It's really better to just use a dll if you need to subclass.

---

I know, hence why I said it is possible. I use ASM in one of my own private scripts... (which is not messy imo though, actually straightforward)

quote:

---

Originally posted by phalanxii
<snip>

---

Thanks for the resource. Even though SOMEONE has to bitch about the hard work you went thru to make a scripter's life easier, I for one appreciate your time and work/effort.

Also big thanks for "TabbedStatusIcon" but if its suppose to work like Veggie's Status Icon, it doesnt. At least not here:
Vista
Plus! 3.60
Messenger 9.0

Well, I certainly have no idea about ASM, but for those who are interested, deAd has explained how to do it in this separate thread.

Anyway, I was browsing around MSDN and found this page explaining how to subclass windows.

It uses the SetWindowSubclass, RemoveWindowSubclass and DefSubclassProc functions from comctl32.dll which comes with Windows XP (?).

Is it possible to use these functions with GetCallbackPtr in order to subclass, or is there still the same problem as using SetWindowLong and GetCallbackPtr?

quote:

---

Originally posted by riahc4
Also big thanks for "TabbedStatusIcon" but if its suppose to work like Veggie's Status Icon, it doesnt. At least not here:
Vista
Plus! 3.60
Messenger 9.0

---

I'm using XP at the moment with Plus! 3.60, but I have had confirmation that it works on Vista too. I don't know whether it works on Messenger 9.0 though, but I see no reason why it shouldn't. Perhaps you need to restart messenger?

quote:

---

Originally posted by riahc4
Also big thanks for "TabbedStatusIcon" but if its suppose to work like Veggie's Status Icon, it doesnt. At least not here:
Vista
Plus! 3.60
Messenger 9.0

---

you can't use 3.60 with 9.0

what is the difference in this script and the Status Icon script?