On 17/03/2008, Marc Weustink <[EMAIL PROTECTED]> wrote: > > Every localizable property will be declared as a TTranslateString (and > not as String).
Ah, I've seen the TTranslateString type around. :) > When such a property is written, the IDE also generates a constant for > it. Then on loading, the lcl catches those properties and will replace > them with the proper translation. Maybe the IDE is trying to hard. Why not create a Property Editor for TTranslateString types. In the Editor the user can specify the resource string identifier and default value. The IDE can then take it from there... If the user simply typed Text in the OI, no resource string identifier is created and it's simply handled as a standard string value. That way, no existing code will be broken (kind-of). Regards, - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ _______________________________________________ Lazarus mailing list [email protected] http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
