07-25-2006 12:33 AM - edited 07-25-2006 12:33 AM
Message Edited by Johan.svensson on 07-25-2006 12:39 AM
07-25-2006 12:34 AM
There is no picture..
07-25-2006 01:25 AM
Right click on the constant . Select Representation fro the popup-menu followed vy double or whatever other type you want.
07-25-2006 01:32 AM
I've tried that now and of course the data type changes, but the tunnel (i belive it is caled tunnel) does have q white spot in the middle which the other tunnels don't
Does it make any difference? I mean, about solving the problem with "minimum scale" property node
07-25-2006 01:34 AM
How to change the type, cubano already described.
Basically it should set the scale, because the datatype is converted (you should see a conversion dot). Maybe you have autoscale activated (I assume you try to set the scale of a graph control), what could result in the described behaviour.
07-25-2006 01:36 AM
Yes this makes a difference - the one you described, passes a default value to the property node. You have to wire these from the inside - this could also cause the described behaviour.
To avoid this, rightclick these terminals and deselect "default values if unwired".
07-25-2006 01:43 AM
In this case an integer input to a floating point property node will not cause any alarming errors.
That white dot in the middle just denotes that you have selected 'use default if unwired' option for that particular tunnel.
if you connect inputs to that tunnel in all event cases, this white dot will disappear.
if you leave it blank, a default value will be assigned from that case to the tunnel
07-25-2006 02:30 AM
There was an unconnected wire in timeout event.
When all got connected and datatype double the scaling of the graph works perfectly