Virtual properties

[Mark Schonewille]

Hi Andrew,

I think you're making it unnecessarily difficult. There are custom  
properties and handlers. A custom property is saved in a stack and  
contains data. A handler is a script. Such a script can set custom  
properties, but not necessarily. Also, if you pass a setprop message,  
a property will be set after the script is run. I never considered a  
getprop or setprop handler virtual, it is just another script. A  
mouseUp message that isn't passed doesn't suddenly become virtual,  
does it?

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer

Economy-x-Talk is always looking for new software development  
projects. Feel free to contact me for a quote.

Op 23 mrt 2010, om 21:00 heeft Andrew Kluthe het volgende geschreven:

>
> I recently decided that my code would be cleaner and not so buggy if  
> I used
> custom properties and property handlers more often instead of global  
> arrays
> and the functions like Percent2Decimal, Validate, yaddayadda to  
> manipulate
> them.
>
>
> Given that, I just don't get the real difference between virtual  
> properties
> and custom properties. Here is what I do get.
>
> Virtual Properties allow you to set/handle other properties without  
> actually
> storing a value? Correct?
>
> Can't you do this in custom properties too? or are they considered  
> virtual
> when you start doing that?
>
> Anything else I should have an understanding of in regards to virtual
> properties? The above is the limit of my assumptions when it comes  
> to the
> differences between custom and virtual.
>
>
> Thanks for the help,
>
> Andrew Kluthe