On Sun, Dec 29, 2013 at 8:15 PM, Graeme Geldenhuys <gra...@geldenhuys.co.uk> wrote: > fpGUI only uses UTF-8 internally, so developers using fpGUI simply use > the functions fpGUI supplies - instead of the FPC RTL ones. eg: use > fpgFindFirst instead of FindFirst. All such functions are the RTL names, > but with a 'fpg' prefix, so makes it easy to remember. They are all in a > single unit too, the fpg_utils.pas unit.
Creating your own set of routines and classes is very easy, but now comes the real question: From what I understand the new Unicode FPC will be a one way ticket to the Delphi solution, which means that TStrings, TComponent, and all other classes will only work with the new string type. So what will you do then? Your current solution just like the current LCL solution will not work. There are only two solutions: 1> Stop using the RTL and write your own 2> Migrate to the new system Which way will fpGUI choose? -- Felipe Monteiro de Carvalho -- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
