Sending class members to functions?

[Coiler]

I'm getting an error when I try to send class member variables to a function - specifically MouseGetPos(). I'm assuming it uses something similar to ByRef on its parameters. The code is simply MouseGetPos( Gesture.PA.X, Gesture.PA.Y ), and the error is "Parameter #1 of MouseGetPos must be a variable." Gesture is a global class, with PA as a nested vector2 class, and X/Y being normal members (I hope) defined in the __New() function as this.X := ***.

I'm new to programming with classes in AHK, but I'm assuming we can normally use member variables as parameters? Am I doing something wrong somewhere? I searched a great deal and could find nothing about this, so I'm hoping I did something incorrectly somewhere. But I've double checked everything.

Is this just because this function captures its args by reference, or perhaps something specific to AHK V2?

Any help is appreciated!

Main part of the vector2 class:

Code: Select all

class XVEC2
{
	; SETUP
	__New(x:=0,y:=0)
	{
		this.X := x
		this.Y := y
	}
}

[BoBo]

TBH, I only know MouseGetPos as a legacy AHK-command (instead of an UDF)???
Might work to 'force an expression' where it expects the variable? Worth a try & yes, I might be wrong
MouseGetPos,% Gesture.PA.X,% Gesture.PA.Y, ...

[kczx3]

Pretty sure they have to be plain variables. You can have it output to class properties.

[SOTE]

Before getting too deep in the weeds with Classes or in carrying over Class-Based OOP thinking from a different language, AHK (like JavaScript and Lua), is a Prototype-Based language (https://en.wikipedia.org/wiki/Prototype-based_programming). Therefore, one should not feel constrained by creating a Class or needing it, in order to use Objects or make scripts. Also the way in which one would use Classes, if you persist that you must or want to, can be a bit different.

This thread with examples, might be useful to read.
https://www.autohotkey.com/boards/viewtopic.php?t=70676
(Base Classname)

[swagfag]

its something specific to ahk in general(and v2, hopefully, only for the time being)
object properties cannot be the target of OutputVar function(command) parameters(fails silently in v1; u get an error in v2)
workarounds are:

• introduce a method that queries the x/y and assigns them to the properties
• or have x/y be dynamic properties whose getters themselves call MouseGetPos() and return the current respective value(downside is more mousegetpos invocations, if that matters. upside is u dont have an additional method to deal with)