On Thu, 7 Mar 2019 00:53:32 +0100
Joe via lazarus wrote:
> Hi,
>
> we control some laboratory equipment with a LabJack U3-HV interface.
> The manufacturer of the interface provided a dll file and a Delphi
> wrapper for the dll file to read and set the ports of the interface.
> This works well wi
The implementation part is missing "stdcall;"
You also need to match the parameters and return types of functions
between interface and implementation parts.
Actually the implementation part is not needed (I think). Just give
the external DLL name in the interface.
Juha
--
___
Hi,
we control some laboratory equipment with a LabJack U3-HV interface. The
manufacturer of the interface provided a dll file and a Delphi wrapper
for the dll file to read and set the ports of the interface. This works
well with Delphi XE2.
But when I try to migrate to Lazarus 2.0, this wra
I cc / reply-to the Lazarus list, since this is not an fpc topic.
On 06/03/2019 20:49, Anthony Walter wrote:
I agree that the hardest part would be detecting project changes. That
is files opened, new files added, packages added or removed and so on.
I think if I could or someone could write so
I have an idea to make LCL based TFontDialog- which will be LCL form,
which can be called by TFontDialog.Execute (if Boolean variable in LCL
is set). Why make it?
- we can make all best features of FontDlgs from all WSes
- we can make additional events- e,g, OnSelectFont (called when used
sel
Op 06-03-19 om 08:52 schreef Bo Berglund via lazarus:
I finally used the poNoConsole flag in the options even though the
Lazarus help specifically states it ONLY works in Win32.
This was probably written when there was no Win64 LCL-widgetset yet. At
that time, 'Win32' was synonymous to 'The Wi
