[Lazarus] Tdbf using Foxpro *.cdx index files

Tdbf can now utilize Foxpro memo fields (*.fpt) but not index files (*.cdx).   Libre Office Base version 5 seems to be able to use these index files.  Since it is open source, perhaps the current Tdbf maintainer can use that to add important *.cdx compatibility to Tdbf? Bob B.--

Re: [Lazarus] Makedeb - how to lower the dependencies

That's our application... now we are going to build it on an older Linux and try again. We are installing Lazarus on a 32-bit Ubuntu 10.04 LTS vmware image just for that. We tried to edit the xml makedeb's file but it gets overwritten every time the .deb is built. So, instead of running makedeb on

Re: [Lazarus] Instalation on win 10

On 04.04.2016 20:21, Pedro Albuquerque wrote: > Hi, > > There has been a while since I used Windows and, more specifically win10 > I never tried. I recently got a new machine, but it runs win10. Are > there any special precautions to take with Lazarus/fpc instalation? > > I mean known issues,

Re: [Lazarus] German umlauts in component names

On 04.04.2016 18:07, Ondrej Pokorny wrote: > On 04.04.2016 16:57, Bart wrote: >> To me it just looks funny to have 2 languages in one file e.g. > > Just a curiosity from FPC code :) > > compiler/tokens.pas: > _LECKKLAMMER (I assume "linke eckige Klammer") > _RECKKLAMMER > _LKLAMMER > _RKLAMMER >

Re: [Lazarus] Makedeb - how to lower the dependencies

On Mon, 4 Apr 2016 15:03:02 -0300 Alexsander Rosa wrote: > I would like to allow the resulting .deb to be installed on older Linux > distros. > > Example on Ubuntu 12.04: > > # dpkg -i rnge3_16.03-i386.deb > (...) > dpkg: problemas de dependência impedem a

[Lazarus] Instalation on win 10

Hi, There has been a while since I used Windows and, more specifically win10 I never tried. I recently got a new machine, but it runs win10. Are there any special precautions to take with Lazarus/fpc instalation? I mean known issues, choosing specific directories for clean and build, etc.? Is

[Lazarus] Makedeb - how to lower the dependencies

I would like to allow the resulting .deb to be installed on older Linux distros. Example on Ubuntu 12.04: # dpkg -i rnge3_16.03-i386.deb (...) dpkg: problemas de dependência impedem a configuração de rnge3: rnge3 depende de libatk1.0-0 (>= *2.10.0*); porém: Versão de libatk1.0-0 no sistema é

Re: [Lazarus] German umlauts in component names

On 04.04.2016 16:57, Bart wrote: To me it just looks funny to have 2 languages in one file e.g. Just a curiosity from FPC code :) compiler/tokens.pas: _LECKKLAMMER (I assume "linke eckige Klammer") _RECKKLAMMER _LKLAMMER _RKLAMMER rtl/inc/text.inc: Procedure

Re: [Lazarus] German umlauts in component names

On 04.04.2016 12:05, Special wrote: BTW too: Some English words became part of german, like 'Computer' und 'Button'. We don't say "Elektronische Rechenmaschine" any longer, and more and more german book authors say "Button" instead of the strange "Schaltfläche". Yes, I confess, I used

Re: [Lazarus] German umlauts in component names

On 2016-04-04 15:57, Bart wrote: > To me it just looks funny to have 2 languages in one file e.g. :) I agree. Even though I developed Afrikaans application at one point, using English in the source code was much more natural and matched the Object Pascal and RTL English language usage. I like

Re: [Lazarus] German umlauts in component names

On 04/04/2016 10:57 AM, Bart wrote: Well, I'm not English and still I do not desire such a feature. I tend to have English names for all procedures/functions/properties/types as well. To me it just looks funny to have 2 languages in one file e.g. the worst that i've seen is delphi code with

[Lazarus] Esc closes modal forms [Qt4]

Hi, this is user-unfreindly issue in Qt4. When I open form as modal (ShowModal) and then I open any combobox there, I sometimes want to leave it without change by Escape key. It closes the combo but at the same time it closes the form. It does not happen in Gtk2 (i.e. I would have to press Esc

Re: [Lazarus] German umlauts in component names

On 4/4/16, Mattias Gaertner wrote: > This is an English mailing list, so naturally you will find many > thinking the same here. > But many people want to use non English words as identifiers. They need > non English letters. Well, I'm not English and still I do not

Re: [Lazarus] German umlauts in component names

Am 04.04.2016 12:12 schrieb "Mattias Gaertner" : > > As funny as the idea of using emojis for identifiers sound as scary it is. > > So I don't really support this. > > I share your concerns about non English keywords. For identifiers I > see some gain. > > Do the linker,

Re: [Lazarus] German umlauts in component names

On Mon, 4 Apr 2016 11:45:02 +0200 Sven Barth wrote: > Am 04.04.2016 11:40 schrieb "Special" : > > What problems, Denis? We use component names like "SchließenButton" since > many years with Delphi in training programs for german pupils. And in

Re: [Lazarus] German umlauts in component names

Am 04.04.2016 um 11:54 schrieb Ondrej Pokorny: On 04.04.2016 11:40, Special wrote: What problems, Denis? We use component names like "SchließenButton" since many years with Delphi in training programs for german pupils. And in code for the international community, we don't use it. Sometimes

Re: [Lazarus] German umlauts in component names

On 04.04.2016 11:40, Special wrote: What problems, Denis? We use component names like "SchließenButton" since many years with Delphi in training programs for german pupils. And in code for the international community, we don't use it. Sometimes it's better to give people less rights. They do

Re: [Lazarus] German umlauts in component names

Am 04.04.2016 11:40 schrieb "Special" : > What problems, Denis? We use component names like "SchließenButton" since many years with Delphi in training programs for german pupils. And in code for the international community, we don't use it. *You* might do this, but others

Re: [Lazarus] German umlauts in component names

Am 03.04.2016 um 06:21 schrieb Dennis: Graeme Geldenhuys wrote: On 2016-04-02 13:16, Santiago A. wrote: similar should be done. You would need to make compulsory a command in source code to tell which code set is using. I would hope anybody in this day and age only uses UTF-8 for text files