backscript and custom properties

[Mark Smith]

Jaques, you're right - the script can still refer to 'me'. I use  
buttons as libraries quite often, and the fact that a button's CPs  
are available can be very useful.

I don't tend to use getProp and setProp handlers in those 'button'  
libraries much - you'd still have to refer to the button's name or  
ID, and I generally just want a libraries commands and function  
available.

I'm not sure what you'd expect a setProp handler to do other than  
modify a property, so I don't think I understand what you mean by a  
'pure' custom property...

Best,

Mark

On 23 Dec 2008, at 17:45, Jacques Hausser wrote:

> Hello everybody
>
> I just discovered accidentally that when a button's script is  
> inserted as a backscript, it doesn't go there alone, but takes with  
> it its custom properties, getprop and tutti quanti.
> That could be very useful... Has somebody some experience with this  
> feature ?
> (I discovered also that the inspector doesn't display the "pure"  
> custom property, but the property as modified by the getprop...  
> that is perhaps not so good).
> Happy Christmas (or any other solstice-linked celebration) to you.
>
> Jacques
>
> ******************************************
> Prof. Jacques Hausser
> Department of Ecology and Evolution
> Biophore / Sorge
> University of Lausanne
> CH 1015 Lausanne
> please use my private address:
> 6 route de Burtigny
> CH-1269 Bassins
> tel/fax: 	++ 41 22 366 19 40
> mobile:	++ 41 79 757 05 24
> E-Mail:	jacques.hausser at unil.ch
> *******************************************
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution