Am Di., 13. Nov. 2018, 07:04 hat Ryan Joseph
geschrieben:
>
>
> > On Nov 12, 2018, at 5:45 AM, Vojtěch Čihák
> wrote:
> >
> > We've already decided internally that we are *not* going to support this.
>
> Why does FPC have Delphi mode anyways? It’s not actually compatible with
> Delphi so what
> On Nov 12, 2018, at 5:45 AM, Vojtěch Čihák wrote:
>
> We've already decided internally that we are *not* going to support this.
Why does FPC have Delphi mode anyways? It’s not actually compatible with Delphi
so what is it used for? It seems like if you’re a Delphi user you would just
use
On 11/12/2018 7:05 AM, Santiago A. wrote:
El 02/11/18 a las 11:13, James escribió:
I've been programming for decades with Pascal, starting with Turbo
Pascal, and for a few years now with Freepascal, and even wrote really
complicated console windows programs with Freepascal that do windows
Thank you! I somehow missed the result of the function being the status I was
looking for. I guess the answer was so easy I couldn't see it
-Original Message-
From: fpc-pascal On Behalf Of
Alexander Grotewohl
Sent: Monday, November 12, 2018 11:10 AM
To:
This line:
Writeln(GetSaveFileNameA(@TFilename));
What does it write when you select a file vs when you click x/cancel?
:-):-)
On 11/12/2018 4:31 AM, James wrote:
I've been using the example below to use the Save-as dialog in my console
program, and it works great, but I would like to be
El 02/11/18 a las 11:13, James escribió:
I've been programming for decades with Pascal, starting with Turbo Pascal, and
for a few years now with Freepascal, and even wrote really complicated console
windows programs with Freepascal that do windows function calls... But now I
find that I would
Am 10.11.2018 um 12:17 schrieb Ryan Joseph:
> This also fails.
I personally find this case much more limiting.
Another implication is that you can't build up consts from other record consts,
such as:
--
type
TMyRecord = record
a:
> On Nov 12, 2018, at 1:55 PM, Sven Barth via fpc-pascal
> wrote:
>
> That is a constructor that takes no arguments. How do you think that is
> useful for a constructor that *does* take arguments? That is absolutely not
> clear at all for the user.
I just meant as a label so you know the
I've been using the example below to use the Save-as dialog in my console
program, and it works great, but I would like to be able to detect if the user
pushes either the red X or the cancel button in the dialog. I am supplying a
suggested default name, and what's happening is if the user
