22 replies to this topic

[derRaphael]

BTW, is this the answer to nubAHK (or inevitable universe balancing) ?
Perhaps you should make a wiki or something

dont be mean.

[majkinetor]

I am just teasing you guys. I might be mean a little bit too

[noee]

First, excellent work on the particular "sugar" for class defn. I'm converting an app that controls my HTPC, love it so far.

Not sure what to make of this. In one class, I am defining properties *and* overriding __Get. When doing this, the override is not working (properties work fine). Bug with the new addition of Properties support?

class Ihtpc....
.
.
.
	property VideoRenderer
		get
		{
			return this.MPC.Video
		}
	endprop
	property AudioRenderer
		get 
		{
			return this.MPC.UseReclock ? this.RC.KS_Device : this.MPC.Audio
		}
	endprop

	method __Get(name)
	{
	  static def, prim
	  ; app specific Playback monitor device
	  if (name="mon" || name="monitor") {
		if !def
		  def := this.displays.defindex
		return this.displays[def]
	  }
	  ; Windows primary monitor device
	  if (name="prim" || name="primary") {
		if !prim
		  prim := this.displays.primindex
		return this.displays[prim]
	  }
	}
.
.
.
endclass

[fincs]

Glad someone found an use for my silly script
Of course your custom __Get handler is going to be skipped as the property __Get handler is at the very end of the Object() call used to create the base object. In your particular case you're using it to make aliases. Perhaps I should implement them?

property monitor alias mon

[Lexikos]

I suggest:

; In place of "alias":
property monitor = mon  ; assert equality, or
property monitor := mon ; assign name

; To allow __Get and __Set to be extended:
property this[params]
{
    ...
}

[noee]

...
Of course your custom __Get handler is going to be skipped as the property __Get handler is at the very end of the Object() call used to create the base object. In your particular case you're using it to make aliases. Perhaps I should implement them?

Okay, yeah, my bad, I wasn't paying attention. Yup, aliases in some form would be useful.

[fincs]

@Lexikos: interesting. I prefer the colonless form of aliasing because using colon+equals suggests variable assignment. As for your other proposal, you also suggested me of implementing indexed properties, just like C#:

property Units[id]
{
    get
    {
        return DllCall(... ..., "int", id, ... ...)
    }
}

Oh, and when I get to implement the v2 syntax I'll make a v1-to-v2 converter.