On 11 April 2010 21:47, Roberto Padovani wrote:
>
> for the virtualization, the problem is the absence of the drivers for
> most of the pc hardware unless you happen to have a pc with the
> very few types of devices used in macs.
Well, virtualization software like VirtualBox "fakes" it's own
2010/4/11 Graeme Geldenhuys :
> On 10 April 2010 19:20, Schindler Karl-Michael
> wrote:
>>
>> I tried a bit more using colorlistbox. But what would be as simple as
>> possible X11 examples? working with gdb is quite tedious.
>>
>
> >From fpGUI point of view, simply creating a single main window w
On Sun, 11 Apr 2010, Graeme Geldenhuys wrote:
On 10 April 2010 16:36, ed...@clanhay wrote:
I am trying to setup an FTP client using the ICS tFTPClient but not have
been too successful.
Any specific reason why it must be ICS components? If you can use
alternative components, then you could
Yes it works, but the {$DEFINE NOFORMSPLEASE} clause must be put in the unit
itself. If I put the clause in the first line of my console project, the unit
won't catch it.
How can I define a compiler directive that can be understood by all units in my
project?
Anyway, thanks.
- Original
On 11 April 2010 12:27, Marco van de Voort wrote:
>
> As long as you realise it is win32(and maybe win64) only, there is no
> problem
That's what I meant about "fpc friendly". As far as I knew ICS was
quite Windows specific, where-as Indy and lNet are not. One never
knows if you are later going t
Thanks Bart, I will try it.
- Original Message
From: Bart
To: FPC-Pascal users discussions
Sent: Sun, April 11, 2010 4:51:54 PM
Subject: Re: [fpc-pascal] (no subject)
Simply define the compiler directive NOFORMSPLEASE when compiling your
console app.
The ProcessMessages is there (I g
In our previous episode, Graeme Geldenhuys said:
>
> Any specific reason why it must be ICS components? If you can use
> alternative components, then you could try Indy or lNet. I believe
> they are more FPC friendly.
ICS actually was the first socketsuite ported. (it was still D1 compatible,
and
Simply define the compiler directive NOFORMSPLEASE when compiling your
console app.
The ProcessMessages is there (I guess) for allowing the Application
object to update screens (WinControls).
Since a console application does not link in LCL this is not necessary.
Bart
On 10 April 2010 16:36, ed...@clanhay wrote:
> I am trying to setup an FTP client using the ICS tFTPClient but not have
> been too successful.
Any specific reason why it must be ICS components? If you can use
alternative components, then you could try Indy or lNet. I believe
they are more FPC fr
On 10 April 2010 19:20, Schindler Karl-Michael
wrote:
>
> I tried a bit more using colorlistbox. But what would be as simple as
> possible X11 examples? working with gdb is quite tedious.
>
>From fpGUI point of view, simply creating a single main window with
nothing in it. A lot still happens in
I have the following part of a unit code which can be compiled successfully
under a normal GUI application.
{$IFNDEF NOFORMSPLEASE}
if soProcessMessages in oSearchOptions then
Application.ProcessMessages;
{$ENDIF}
My question is, how can I use this unit from my console application? I k
11 matches
Mail list logo
