I have moved from a multi-card model to a one card script-driven-data presentation model, in large part due to this very issue. But sometimes it would be just a whole lot simpler to use multiple cards -- but the lack of inheritance means that one ends up writing such silly but unfortunately required fix it scripts, like
repeat with x = 1 to the number of cards repeat with y = 1 to the number of fields of card x set the textfont of fld x to "Verdana" end repeat end repeat
when, one should be able to simply change the font for the stack.... But perhaps it was a good thing as it drove me to the one card -script-drive-data hide and show groups, fields etc. presentation model. where one only has a single set of fields on one card that required modification. So that was a good outcome... But this assumes an extremely consistent ordered, xml style structure for the data in a custom property, and often this may not be the case for the material in hand and multiple cards with a variety of different fields and variable text are needed and they really should all inherit and not copy down, all text properties.
Sannyasin Sivakatirswami Himalayan Academy Publications at Kauai's Hindu Monastery [EMAIL PROTECTED]
www.HimalayanAcademy.com, www.HinduismToday.com www.Gurudeva.org www.Hindu.org
On Nov 22, 2003, at 5:46 AM, Ken Ray wrote:
This is because when the style of the field was set to bold, the font and size (Times New Roman 14) were copied into the field, and the inheritance connection was broken. So when you change the textFont of the card to Monaco, the field doesn't inherit it anymore.
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
