attachment-0001

<html> I have concerns about the performance impact of having to scan for dynamic changes every time something in the UI changes. The UI code could build tables to keep track of where dynamic strings exist but this seems like a lot of work just so someone doesn't have to create a few more UPDF localized strings. Jim At 5/11/01 12:55 PM, Norbert Schade wrote: <blockquote type=cite cite>The Name_ID in the technical description is providing the reference to the Locale_Element in the locale file. In many cases the Locale_Element shows a term, which is to be shown unproved in the UI. Especially when there is a chance to specify only one record with a formula for a feature instead of many records with single entries, it seems very useful to be able to have the Parameter Converter (in case you are not too familiar with it: the Parameter Converter helps converting formulas to real entries) help to build the UI string. Samples could be copies, zooming percentage, resolution, etc. We are a little concerned about performance, as this has to happen dynamically every time. Let's discuss that on the distributor. Send your opinion to the group.   Regards Norbert Schade Principle Software Engineer Host Software Group Oak Technology, Inc. 10 Presidential Way Woburn, MA 01801 USA Phone: 1-781-638-7614 Fax: 1-781-638-7555 email: <a href="mailto:norbertschade@oaktech.com">norbertschade@oaktech.com</a> </blockquote></html>