QUOTE(Starrider @ 03/23/09, 10:48 PM) [snapback]303746[/snapback]
Sorry but that's wrong. C just uses double as a standard.
No its correct. Im not talking about C im atlking about maya. Mel doesnt diferetiate between floats and doubles For MEL theres only FLOAT which is equal to double or float in c whatever happns to be there. Thus the node refenerce is not entirley clear on the subject BECAUSE ITS WRITTEN FOR MEL (and not for c++, so maya manual is not written under the assumprion theres a difference, only your code is). So so sometimes they refeer to doubles and other times floats they mean the same thing form your point of view.
Ergo:
QUOTE
Because in C the term float means something else.
In C thares those 2 terms. Not maya manual for other than API part
The node reference is not entirely exact on the wording most of the time it doenst need to its not meant to be precice for C++ developpers, in most cases the float arrays are double arrays. Its because mel doesnt differentiate things. Anyway not all things that can be connected in according to the reference work out at all.
Because the node may have some unexpected assumptions on the attributes in question. So even if you connect it and it dont seem to work doent mean you have the worng type in play, as maya does conversions automatically. It can just simply mean the node does expect the data to be static, thus changing the data means nothing.
There are several such nodes available where the node refernce says you could connect but it doenst do anything. And there are several where they sy you cant connect and you in fact can.
This said there is actually one node im aware of that does differebntiate between the 2 possibly by programmer not knowing this mistake. And thus that cannot be connected to. Maybe youve stumbled uppon a second such thing. You can see it if maya refuses to connect. However if it connects but nothing happens then your just out of luck the node sees you as static and leaves at that. Or your initial size is wrong and it excepts you out.
on a related note: Its not also allways clear WHERE the data gets injected solmetimes nodes work like this
input read
input read
input read
computed
output
But sometimes they work like this:
input read
computed
output
input read
computed
output
input read
computed
output
in wich case its possible to inject code between the inputs if you happen to know the order.
BUT then theres a few nodes in the minority thet work like this
input read
computed
input read
computed overrides
input read
computed overrides
output
Wich dont make sense to connect into the 2 fiorts ports, why they exost don't seem to make sense. But they are used on load form maya binary format. Usually its stated but not allways.
So whether or not it works out is purely random.
