Graeme Geldenhuys schrieb:
As mentioned some time ago, CodeGear and FPC/Lazarus could cooperate
very well, and together they could place alternative multi-platform
BTW: I don't believe CodeGear exists any more.
I'm not sure, but IMO now it's a daughter of Embarcadero.
Embarcadero on the o
Hans-Peter Diettrich wrote:
>
> As mentioned some time ago, CodeGear and FPC/Lazarus could cooperate
> very well, and together they could place alternative multi-platform
BTW: I don't believe CodeGear exists any more. Embarcadero on the other
hand doesn't seem to have any incentive in cooperati
Marco van de Voort wrote:
>
> Problem is that CHM can emulate .hlp basic topic retrieval, and that's
And why must that problem become FPC's problem? FPC is meant for
multiple platforms, not just Windows platform. So solutions should be
based on what makes sense in a cross-platform way.
> But wh
On Fri, Nov 06, 2009 at 11:36:54AM +0200, Graeme Geldenhuys wrote:
> Mattias G??rtner wrote:
> >
> > Lazarus type signature: THelpEvent = function(Command: Word; Data:
> > PtrInt; var CallHelp: Boolean): Boolean of object;
> >
> > Where Data is PHelpInfo. It is used by the widgetsets.
>
> And wh
Mattias Gärtner wrote:
>
> Lazarus type signature: THelpEvent = function(Command: Word; Data:
> PtrInt; var CallHelp: Boolean): Boolean of object;
>
> Where Data is PHelpInfo. It is used by the widgetsets.
And which seems the same as FPC's THelpEvent, except for the type of the
Data parameter. A
Zitat von Graeme Geldenhuys :
[...]
Here is the difference
Kylix 3 type signature:
THelpEvent = function(HelpType: THelpType; HelpContext: THelpContext;
const HelpKeyword: String; const HelpFile: String;
var Handled: Boolean): Boolean of object;
Free Pascal & Delphi type s
The fpc-pascal mailing list seems to quite for this discussion and
Lazarus would have a greater impact on the suggested change, so I moved
the conversation no Lazarus mailing list instead. Even though THelpEvent
is defined in FPC (not Lazarus).
Yesterday I found that the THelpEvent definition in K