Re: [fpc-pascal] fcl-report demos - expressions - have problem with [RecNo]

2019-12-27 Thread Michael Van Canneyt
On Fri, 27 Dec 2019, Andreas Frieß wrote: There is more not working in the report demos. The expressionparser have problems with a simple [RecNo] Syntax for recno changed, fixed in rev. 43800 Michael. ___ fpc-pascal maillist - fpc-pascal@lists.f

Re: [fpc-pascal] Fwd: Re: fcl-report demos not working on windows10/64 with win64 compiled - Font Arial not found

2019-12-27 Thread Michael Van Canneyt
Hello, Can we please tackle one problem at a time ? The first problem is: Why is the "liberation sans" not found ? Once we've established that, we can check why the fallback is not found, and perhaps the error message. Michael. On Fri, 27 Dec 2019, Andreas Frieß wrote: Hello Michael, if t

Re: [fpc-pascal] Interface delegates and the implements property specifier

2019-12-27 Thread Ryan Joseph via fpc-pascal
> On Dec 27, 2019, at 1:39 PM, Adriaan van Os wrote: > > etcetera. The disadvantage of this approach is that for example a default > DoKeyCommand must be written three times, for TApplication, TDocument and > TView, where the code for TDocument.DoKeyCommand and TView.DoKeyCommand is > identi

Re: [fpc-pascal] Interface delegates and the implements property specifier

2019-12-27 Thread Adriaan van Os
Ryan Joseph via fpc-pascal wrote: Adriaan, what was your idea you had in mind when you brought this up? Well, to give you an idea, here is an example (somewhat simplified for clarity). I am currently porting MacApp to 64-bit. MacApp currently has TView = class( TEventHandler) Howev

Re: [fpc-pascal] Interface delegates and the implements property specifier

2019-12-27 Thread Ryan Joseph via fpc-pascal
> On Dec 27, 2019, at 10:29 AM, Ryan Joseph wrote: > > It's really just about the namespace and avoiding deeply nested this.that.do > kind of syntax. We could accomplish this using just plain records, no need to > even get involved with the complicated interface syntax. According to the > wi

[fpc-pascal] fcl-report demos - expressions - have problem with [RecNo]

2019-12-27 Thread Andreas Frieß
There is more not working in the report demos. The expressionparser have problems with a simple [RecNo] D:\data\lazdev\trunk64\fpcsrc\packages\fcl-report\demos>fcldemo -d expressions Exception at 000100096E0D: EExprParser: Expected ( bracket at position 12, but got -. Heap du

[fpc-pascal] Fwd: Re: fcl-report demos not working on windows10/64 with win64 compiled - Font Arial not found

2019-12-27 Thread Andreas Frieß
Hello Michael, if the font is not found, why is there not the correct indication of the missing font ? The errormessage is in this case completly wrong. If a fallback should be possible, it should work and not mask the problem and create a false errormessage. Maybe the font liberation Sans is n

Re: [fpc-pascal] Interface delegates and the implements property specifier

2019-12-27 Thread Ryan Joseph via fpc-pascal
> On Dec 27, 2019, at 10:01 AM, Sven Barth via fpc-pascal > wrote: > > To be clear: with declaration time I mean when the type is written (" = class > ... end") versus creation time (either "var x: tmyclass" or "x := tmyclass > .create"). The difference would be that the user of the class wo

Re: [fpc-pascal] Interface delegates and the implements property specifier

2019-12-27 Thread Sven Barth via fpc-pascal
Am 26.12.2019 um 20:32 schrieb Ryan Joseph via fpc-pascal: On Dec 24, 2019, at 1:16 AM, Sven Barth via fpc-pascal wrote: Basically, yes, though of course syntax, implementation and behavior need to be nicely defined first. For example there is the difference whether something is added at d

Re: [fpc-pascal] Interface delegates and the implements property specifier

2019-12-27 Thread Ryan Joseph via fpc-pascal
> On Dec 27, 2019, at 8:21 AM, Adriaan van Os wrote: > > The code of a "mixin" or "trait" or "delegate" (or whatever > implementing-something) can be referenced and it can put virtually into the > namespace of an object. The one thing you cannot do however, is copy the > code, because then t

Re: [fpc-pascal] Interface delegates and the implements property specifier

2019-12-27 Thread Adriaan van Os
Ryan Joseph via fpc-pascal wrote: - Importing fields/properties is easy because we can just add symbols to the symbol table but I'm not sure what it means in terms of the compiler to import a method from another class. The method needs to be cloned or perhaps synthesized as I've seen the term

Re: [fpc-pascal] fcl-report demos not working on windows10/64 with win64 compiled - Font Arial not found

2019-12-27 Thread Michael Van Canneyt
As I said: The demos do not use Arial on purpose. Probably it is used as a fallback somewhere. So the question is: why is the demo falling back to Arial ? It means the actually used font (Liberation Sans, line 74 of rptjson) is not found. Michael. On Fri, 27 Dec 2019, Andreas Frieß wrote:

Re: [fpc-pascal] fcl-report demos not working on windows10/64 with win64 compiled - Font Arial not found

2019-12-27 Thread Andreas Frieß
The reason (with ReadStandardfonts inserted): --- D:\data\lazdev\trunk64\fpcsrc\packages\fcl-report\demos>fcldemo -d jsondata -f pdf 0 : Name -> Afghanistan 0 : Population -> 31628000 0 : Name -> Afghanistan 0 : Population -> 31628000 0 : Name -> Afghanistan 0 : Population

Re: [fpc-pascal] fcl-report demos not working on windows10/64 with win64 compiled - Font Arial not found

2019-12-27 Thread Michael Van Canneyt
On Fri, 27 Dec 2019, Andreas Frieß wrote: I have now built the fcl-fpreport demos on win64 on a Windows10/64 machine. But the demo is not running (comandline with -d jsondata -f pdf), because the font Arial is not found. It looks like the demos didnt use the gTTFontCache.ReadStandardFonts and

[fpc-pascal] fcl-report demos not working on windows10/64 with win64 compiled - Font Arial not found

2019-12-27 Thread Andreas Frieß
I have now built the fcl-fpreport demos on win64 on a Windows10/64 machine. But the demo is not running (comandline with -d jsondata -f pdf), because the font Arial is not found. It looks like the demos didnt use the gTTFontCache.ReadStandardFonts and so the standard font is not found. If i chang