Shoutbox

psst, correction:

quote:

---

Originally posted by TheGuruSupremacy
The Function patch was made by me not by Cookie.

---

Sorry, but if you want to talk origins and be precise, then the patch function like it is written was actually made by me. (so are the many other code flows like the SignIn function etc, which are all almost literally copies of what I did before in my memory patching scripts). See all my patch scripts where I used the exact same code.

The patch functions in your NudgesToolScript and Idle Liar scripts for example are also a word for word 'copy' of the one I used in Auto-Emoticons, Unlimited Nudges, etc... including the variable names (but minus the comments from my scripts).

Not that I didn't wanted you to copy them though, but correct is correct

---

and the code:

code:

---

var Handle = Interop.Call("Kernel32","GetModuleHandleW",null);
    var sBuffer = Interop.Allocate(PatchOld.length);
    Address = (Address - 0x00400000) + Handle;

---

Can't be 'be stolen' because it is almost strait forward stuff to convert a base address to the correct virtual address in case the module is loaded in a different base offset. Nothing unique at all. It is (should be) used in almost every program and script which deals with memory patching (although not always like in my scripts where I simply ignore the possebility ). It is in fact a mandatory step for such programs and thus should be common knowledge* and can not be owned or be claimed that "someone came up with it" or "invented it" and thus "stole it". It's another thing when someone (eg: TB) points out the nessecity of it of course.

provided he who put that code in his program/script knows what it does and why it is there of course. Otherwise it is just plain script-kiddy copying (but still not "stealing unique code" imho).

---

All and still with huge respect to TheGuruSupremacy though

---

quote:

---

Originally posted by NanaFreak
this can be easily done with the registry setting made available by Patchou with MP!L.

see Messenger Plus! Live - Registry Settings and search for "OverrideImgTransfer"

a simple .reg file would be all that is required to fix the issue...

---

No, that registry setting will not completely disable Photo Sharing....
This script does...

see OverrideImgTransfer and photo sending
in which you actually corrected the OP and said the exact same thing I do now: that the registry key does not completely disables Photo Sharing; it only disables Photo Sharing for pasted image data, not for dropped graphic files

---

PS: master4523, I suggest to change this:

code:

---

MsgPlus.DisplayToast("Photo Sharing", "Windows Live Messenger " + Messenger.Version.toFixed(1) + ".0" + Messenger.VersionBuild + "\nis not supported");

---

to:

code:

---

MsgPlus.DisplayToast("Photo Sharing", "Windows Live Messenger " + Messenger.Version.toFixed(1) + "." + ("000" + Messenger.VersionBuild).slice(-4) + "\nis not supported");

---

Since the buildnumber isn't always a 3 digit number anymore (since a long time actually).

Also, the function OnGetScriptCommands() is wrong in your code. You don't have any commands in your code to begin with.

And you might want to store the setting user specific, not globally (thus by using Messenger.MyUserId).

And I hope you didn't just blindly copied all the code from my scripts and from TheGuruSupremacy's scripts without understanding what it all does.