Page 1 of 1

Problems with Variable component

Posted: Mon May 20, 2013 2:00 pm
by Rado1
1. If defined a Variable component, e.g., call it var of type int, the content assistant offers on "var." possibilities such as: ByteValue, IntValue, ManagedValue, ... but if put to the expression, e.g., var.IntValue, syntax error "Could not determine type: IntValue" occurs. Content assistant should not offer these possibilities.

2. How to assign to a variable of type vec* defined as Variable component? For instance, for var defined as vec2, var[0] returns syntax error "Identifier is not an array: ManagedValue". This is probably an error.

Posted: Tue May 21, 2013 11:18 am
by VilleK
Hi,

The second issue is now fixed. Please download the beta again.

Posted: Tue May 21, 2013 1:05 pm
by Kjell
Hej Ville,

If & when you're going to tackle the first point that Rado1 brought up, please consider looking at the suggestion i made in the Beta thread concerning the Variable component ( even though i'm aware the solution for the auto-completion "thing" doesn't have anything to do with the property panel )? :)
Kjell wrote:Would it be possible that the properties panel of the Variable component changes depending on what Type is chosen ( see attached mock-ups )? Right now only floats can be modified, and the type-specific read-only properties might confuse beginners.
Image

K

Posted: Mon May 27, 2013 4:27 pm
by Rado1
Hi Ville, there's probably a bug in accessing vec3 variables, which sometimes throws an access violation. Try to run the attached project.

Posted: Tue May 28, 2013 8:05 am
by VilleK
Hi Rado1. Yes it was a bug. Please download the beta again.