Question about setting an Attribue/property

[PLUCKYHD]

Lets say I have an attirube/property "A" and a changing attribute "PropertyName" and I want to set that attribute based on another attribue for instance. Let's use an options menu for true or false settings.

Setting = GetProperty("A",false)

PropertyName = "A"

I then want to say

Property = !setting (but I want property to set the value of "A" not property)

is this possible?

[stanger89]

You mean like this:

prop1 = GetProperty("prop1", false)
prop2 = SomeRandomPropertyName()
SetProperty(prop2, not(prop1))

I think that should work... Though I don't remember if you can use the bang (!) to negate, or if there's a "not" keyword, or if you're going to have to resort to and if/else block.

[PLUCKYHD]

Originally Posted by stanger89

You mean like this:

prop1 = GetProperty("prop1", false)
prop2 = SomeRandomPropertyName()
SetProperty(prop2, not(prop1))

I think that should work... Though I don't remember if you can use the bang (!) to negate, or if there's a "not" keyword, or if you're going to have to resort to and if/else block.

I am not trying to set the property thought it is just an attribute it does work if I am setting a property.

[stanger89]

You mean you want a dynamically named attribute to be set to the value of a property? I don't know how to do dynamically named attributes. That or I'm still not sure what you're going for

[GKusnick]

Attributes and properties are two completely different concepts. Properties are configuration data that persists from one session to another; they're accessed via the GetProperty and SetProperty API methods.

Attributes are temporary variables for storing arbitrary data within a session. They're declared using Attribute widgets and accessed just by using their name in an expression.

Since an attribute can contain any data you like, it can of course contain the value you get back from a call to GetProperty. Similarly, you can pass any arbitrary value to SetProperty, including the value of an attribute. But that's true of any expression; there's nothing special about the relation between attributes and properties.

If what you're looking for is a way to store a collection of related values indexed by name (instead of by number), a low-tech way to achieve that is with a case statement (as I pointed out in a previous thread). A better approach would be to use a Hashtable or HashMap.

If that's not what you're looking for, maybe you could explain in more detail what you're trying to accomplish, and somebody can then suggest a better way of doing it.