Thorsten Bosbach wrote:
...
I would love to see the KeyID connected to a string in every OOo build.
This would also make it easier to find a string in the database - even
if the database is not public and even if it is not a KeyID build.
The id could be made visible with the declare.bas tool ? - Instead of
the current variant by printing the KeyID next to the string in the UI.
Yes I would too and the people doing the KeyID Builds would like to
spend their time for other things too.
For the UI Elements this could be done by storing the number in some
special place in the resource files (*.res) and the UI Element.
but whenever there is a String resource (just a string not connected to
a UI element) it is not predictable in which way it is changed till it
is displayed in the UI.
E.g. the names for formulas are seen in conjunction with parentheses
'(',')' or a leading equal sign '='. maybe with other nested functions.
So how should the connection be made to a certain KeyID. Holding a list
of IDs in the String sounds a bit too expensive in terms of runtime and
implementation time. The runtime might be tolerable in a debug build but
not elsewhere.
Another problem is that sometimes strings just get written to a Window,
so the connection from the Window to the sting(and the KeyID) is hidden
somewhere in the implementation and noone will spend the time to
implement special methods to reveal this connection.
So doing KeyID builds seems to be the only way to achieve what we want.
Regards
Gregor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
