Send a param with catchEvent?

[MrOmega]

is it possible to send a param with catchEvent?

such as I have these in a GuiShowImgCtrl of a character

PHP Code:

thiso.catchEvent( name, "onMouseDown", "RotateChar");  
thiso.catchEvent( name, "onRightMouseDown", "RotateChar"); 


in the function 'rotateChar' I can't determine which button was clicked as leftmousedown returns false.

I know I could make two short functions but I was wondering if I could combine them. Both attempts when I try to send a param fails to get the event, my question is moreso how to determine which mouse button was pressed?

[cbk1994]

afaik it's not possible without separate functions

use this instead of name when you're catching events.

PHP Code:

thiso.catchEvent( name, "onMouseDown", "RotateChar");  
thiso.catchEvent( name, "onRightMouseDown", "RotateChar"); 


should be

PHP Code:

thiso.catchEvent( this, "onMouseDown", "RotateChar");  
thiso.catchEvent( this, "onRightMouseDown", "RotateChar"); 


the name stuff only works through some silly guessing stuff in the engine (same reason profile = "ProfileName" works?).

[MrOmega]

Originally Posted by cbk1994

the name stuff only works through some silly guessing stuff in the engine (same reason profile = "ProfileName" works?).

So is using 'this' just more efficient than 'name'? Or is it just a preference choice and trivial?

[cbk1994]

Originally Posted by MrOmega

So is using 'this' just more efficient than 'name'? Or is it just a preference choice and trivial?

It's not personal preference, it's the proper way to do it. You're giving it a string when it's expecting an object.

Proof, from a wiki article written by Stefan:

PHP Code:

//#CLIENTSIDE
function onCreated() {
  // Retrieve the playlist via http
  this.req = requestURL("[link removed]");
  catchevent(this.req,"onReceiveData","onData");
} 


[salesman]

I'm pretty sure when you catch an event you'll get the same arguments as when you just handle the event directly (i.e. MyControl.onMouseDown(...)). And the first argument for onMouseDown() is the mouse button iirc:

PHP Code:

thiso.catchEvent(this, "onMouseDown", "RotateChar");

//...

function RotateChar(butt) {
  if (temp.butt == "right") {
    // stuff
  }
} 


[0PiX0]

Why does the wiki show it as:

catchevent(str,str,str)
adds an event handler for the specified object name and event, third parameter is the name of the function which receives the event (first parameter of the event will be the object for which the event occured)

http://www.graal.net/index.php/Creat...ient/TGraalVar

[cbk1994]

Originally Posted by 0PiX0

Why does the wiki show it as:

http://www.graal.net/index.php/Creat...ient/TGraalVar

The wiki is wrong. It also endorses such travesties as using quotes around a GUI profile.

I suppose I could be wrong about this, but it seems very unlikely to me that Stefan would accept the name of an object rather than the object. It's like sending the player's account to a function instead of the player object—it doesn't make sense.

In addition,

Originally Posted by scripthelp

TGraalVar.catchevent(str, str, str) - adds an event handler for the specified object and event, third parameter is the function which receives the event (first parameter of the event will be the object for which the event occured)

[WhiteDragon]

It would be funny if it coerced the object into its name, and then back into an object to actually apply the relevant changes to it in order to catch the event.

[MrOmega]

My whole question is, if it works, why is it allowed? I do use quotes for guiProfile names too, just purely because it highlights the names. Which I like.

[WhiteDragon]

Originally Posted by MrOmega

My whole question is, if it works, why is it allowed?

GS2 is dynamically typed, so values are coerced based on whatever type they need to be. It's usually a Bad Idea™ to rely on the coercing though because it is sometimes unclear what is happening.

For example, you can check if a value exists like this:

PHP Code:

if (temp.someValue) {
// ...
} 


However, what is really happening there, is temp.someValue is being coerced to a boolean (true/false). It will actually coerce to false in the case of say, temp.someValue = "0" or temp.someValue = 0, thus making the if statement not work even though the value does exist.

Basically, relying on the coercing can make strange bugs crop up in edge cases that are hard to find until they actually break something. It's usually best to be explicit.


I personally dislike dynamically typed languages and think they should slowly fade out of existence.