> support fields with state=virtual. Does anybody know if there a specific
> reason for this or is just not there since nobody wanted if before ?
It was introduced because virtual field cannot be changed (well, not normally), so in general, dove does not return virtual fields.
However, in the latest version of Dove, if you _specify_ a field to be loaded, it should do so, regardless of field type or state.
In the editwizards, this means:
<action type="load">
<relation destinationtype="x" role="y" />
</action>will only return a node's persistent fields (not load any virtual fields), but
<action type="load">
<relation destinationtype="x" role="y" />
<field name="z" />
</action>
[Peter Reitsma] Using a 14 july build the virtual field does not raise an error in the EditWizards but the executeFunction() method I wrote to provide for virtual field value is not executed either. Only for the function "gui".MMObjectBuilder JavaDoc mentions for the getValue() method that when no persistent field can be retrieved a call is done to executeFunction() method. Somehow I just do not see this happen. Dove is retrieving field values through the NodeManager and I suppose NodeManager is using the MMObjectBuilder.getValue() method but I might be all wrong.
Upon leaving the EditWizard I get an "No node with fid=f_9 could be found " error message.
will - iirc - only load field z, regardless of whether 'z' is a virtual field or not.
'z' should, however, be a true field of the NodeManager (defined in builder xml, or in the builder code).
I think this code change was made in 1.6.4.
Pierre
