Topic: Calculated library fields shouldn't be editable (Read 1159 times)

tombert · « **on:** January 03, 2010, 12:20:04 pm »

This is'nt a bug, but it's confusing when MC allows to edit fields which are of a calculated expression ...

thx
tom

gappie · « **Reply #1 on:** January 03, 2010, 12:21:44 pm »

This is'nt a bug, but it's confusing when MC allows to edit fields which are of a calculated expression ...

thx
tom

its a bug imo and indeed confusing. and i reported it a while back.

gab

gappie · « **Reply #2 on:** January 03, 2010, 04:46:44 pm »

just had a thought, and its more interesting, actually. it is an other setting that leaks over from the 'user data'. when you go to the calculated field and set it to user data, and the edit type to 'can not be edited', save and close options, and go back and set it to calculated again, the field behaves as expected.

it is really important at this moment to first set the 'data type' and apparently also the 'edit type' and save it before making a calcultad data field.
about the data type setting:
http://yabb.jriver.com/interact/index.php?topic=54226.msg374211#msg374211
http://yabb.jriver.com/interact/index.php?topic=55132.0
http://yabb.jriver.com/interact/index.php?topic=55276.0

imho it is a bit of a mess.

gab

INTERACT FORUM