onCall Event

[Inverness]

I was thinking that an object.onCall() event would allow you to define what happens when you call object() like a function. Obviously this would be a blocking event. I haven't yet decided what I could use it for but I thought it might be nice.

Edit:

And some other things I mentioned before:

A throwevent(objectname, eventname, params...) that throws an event that can be caught with catchevent() like it does with Gui Controls.

onGetVariable() and onSetVariable() events that would allow you to define function behavior for certain variables. Obviously there would need to be some way to specify which variables are included in this.

[Skyld]

Originally Posted by Inverness

I haven't yet decided what I could use it for

Not practical enough!

[Inverness]

Originally Posted by Skyld

Not practical enough!

Perhaps you should ask people what they use __call__() in Python for.

[Skyld]

Originally Posted by Inverness

Perhaps you should ask people what they use __call__() in Python for.

Called when the instance is ``called'' as a function; if this method is defined, x(arg1, arg2, ...) is a shorthand for x.__call__(arg1, arg2, ...).

Strikes me that we can probably already achieve something similar with careful use of function prototyping.

[Inverness]

Originally Posted by Skyld

Strikes me that we can probably already achieve something similar with careful use of function prototyping.

Sounds complicated and more difficult than doing x.functionname();

I also thought of something else I wanted to add but reading your post made me forget it.

[Skyld]

Originally Posted by Inverness

I also thought of something else I wanted to add but reading your post made me forget it.

Tehe. I do quite like your idea of something along the lines of throwing catchable events, though (or patching trigger() to do it properly - last I checked it didn't).

[Admins]

The events for trigger() and normal GUI/player/catchevents are separate for security reasons. In the next Graal version it's however possible to trigger() events to yourself which act like normal GUI events. That is mainly for scripting new types of GUI controls, e.g. you can trigger("onSelect").

[Inverness]

Originally Posted by Stefan

The events for trigger() and normal GUI/player/catchevents are separate for security reasons. In the next Graal version it's however possible to trigger() events to yourself which act like normal GUI events. That is mainly for scripting new types of GUI controls, e.g. you can trigger("onSelect").

If triggering an event on yourself makes it so an outside object can catch the event then that is exactly what I want.

And I hope this works serverside too?

[Admins]

Server-side it's already working for a few months.