On 15.01.2012 16:13, Uli Schlachter wrote: > On 14.01.2012 13:29, Anurag Priyam wrote: >> On Fri, Jan 13, 2012 at 10:20 PM, Uli Schlachter <[email protected]> wrote: >>> On 13.01.2012 15:17, Anurag Priyam wrote: >>> Alternatively someone could come up with a magic way to modify >>> common/luaobject.c so that lua code can add arbitrary properties to an >>> object. >>> That'd be nicer, but I don't see that happening any time soon. :-( >> >> +1. This would be super awesome. I am completely oblivious to the >> lua-C interface, but still, how do you think can one approach this? > > Hm. Each object would need an "auxiliary" table. luaA_class_index() and > luaA_class_newindex (both in common/luaclass.c) would then have to re-direct > the > operation to that auxiliary table instead of calling [new]index_miss_property. > > I'll see if I can do this.
I'm no longer sure if I really want this. The current situation makes sure that one more easily notices that e.g. a client is not a "normal" table and it catches typos. I think extra properties should be implemented in lua (see awful.client.property.set and .get and the same in awful.tag). However, that's totally unsuited for the original idea in this thread (adding a .screen to drawins). So I guess just a new patch which fixes this problem via the new screen.by_coords(x, y)? Cheers, Uli -- "Engineering - where the semi-skilled laborers execute the vision of those who think and dream. Hello Oompa-Loompas of science." -- To unsubscribe, send mail to [email protected].
