To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=22167
------- Additional comments from [EMAIL PROTECTED] Mon Oct 23 03:29:31 -0700 2006 ------- AW: I took a 2nd look. The former error, that the user setting in the measure dialog was ignored, is fixed. What You describe here is a 2nd effetc (which has nebver been changed). The strings are created by SdrModel::TakeMetricStr which uses pre-calculated values which mediate between internal measurements (pool) and UI measurements. Those are bUIOnlyKomma, aUIUnitFact, nUIUnitKomma and aUIUnitStr. nUIUnitKomma contains the maximum allowed comma for different UI settings and is calculated (as the others) in SdrModel::ImpSetUIUnit(). As can be seen in SdrModel::TakeMetricStr(), there is only taken action when the user wants LESS places after comma, but no mechanism if he wants more. I guess the nUIUnitKomma shall describe the maximum possible decimal pcaces after comma for the used combination of model unit and UI unit. I think this is a relict from the integer times where those definitions were made and implemented. Problem is that this is a dangerous place to make changes to, it is the central place where all the measurement decisions are made and the strings are created. AW: The central question is: What may happen when SdrModel::TakeMetricStr() will suddenly return strings with more decimal places after comma than nUIUnitKomma allows? --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
