2.1.0 on Catalina doesn't have this problem for what it's worth.
> On Dec 13, 2019, at 9:19 AM, Michael Van Canneyt via lazarus
> wrote:
>
>
> Hello,
>
> The 'Install packages' dialog has 2 edit boxes to filter the list of
> installed or not yet installed packages. On MacOS, I can type in
lcl/graphics.pp
procedure PolyBezier(Points: PPoint; NumPts: Integer;
Filled: boolean = False;
Continuous: boolean = False); virtual; {$IFDEF
HasFPCanvas1}reintroduce;{$ENDIF}
procedure PolyBezier(const Points: array of TPoint;
El 13/12/19 a les 17:10, Mattias Gaertner via lazarus ha escrit:
On Fri, 13 Dec 2019 16:52:36 +0100
Luca Olivetti via lazarus wrote:
El 13/12/19 a les 16:41, Mattias Gaertner via lazarus ha escrit:
On Fri, 13 Dec 2019 16:24:26 +0100
Luca Olivetti via lazarus wrote:
[...]
But then it
On Fri, 13 Dec 2019 16:52:36 +0100
Luca Olivetti via lazarus wrote:
> El 13/12/19 a les 16:41, Mattias Gaertner via lazarus ha escrit:
> > On Fri, 13 Dec 2019 16:24:26 +0100
> > Luca Olivetti via lazarus wrote:
> >
> >> [...]
> >> But then it has the same problem: even if the form is active,
El 13/12/19 a les 16:41, Mattias Gaertner via lazarus ha escrit:
On Fri, 13 Dec 2019 16:24:26 +0100
Luca Olivetti via lazarus wrote:
[...]
But then it has the same problem: even if the form is active, the
exception could come from somewhere else.
Do you want the call stack?
I know how to
On Fri, 13 Dec 2019 16:24:26 +0100
Luca Olivetti via lazarus wrote:
>[...]
> But then it has the same problem: even if the form is active, the
> exception could come from somewhere else.
Do you want the call stack?
Mattias
--
___
lazarus mailing
El 13/12/19 a les 15:51, Michael Van Canneyt via lazarus ha escrit:
BTW, is there a way to know where the exception came from? I don't see
any method in Exception to do that, and that's the only parameter that
OnException sees (Sender is nil when I raise an exception inside a form).
My use
On Fri, 13 Dec 2019, Luca Olivetti via lazarus wrote:
At least, that is how I see it. Not 100% accurate, but it does the trick
for my understanding ;-)
Yes, I know all of that, but the message loop could also fake re-raising
the exception if it was raised in the context of a ShowModal
El 13/12/19 a les 15:10, Michael Van Canneyt via lazarus ha escrit:
On Fri, 13 Dec 2019, Luca Olivetti via lazarus wrote:
Because ShowModal must run the application message loop, and that
already catches the
exceptions. This is in line with the event-based architecture. It's
the same in
Hello,
The 'Install packages' dialog has 2 edit boxes to filter the list of
installed or not yet installed packages. On MacOS, I can type in the left
edit field to filter the list of installed packages. But I cannot type in
the right edit box. This is a reproducible problem for me.
This is a
On Fri, 13 Dec 2019, Luca Olivetti via lazarus wrote:
Because ShowModal must run the application message loop, and that
already catches the
exceptions. This is in line with the event-based architecture. It's the
same in Delphi.
Yes, I would expect that with Show, but ShowModal is
El 13/12/19 a les 10:38, Michael Van Canneyt via lazarus ha escrit:
On Fri, 13 Dec 2019, Luca Olivetti via lazarus wrote:
Hello,
I don't remember if I asked this previously, but it always bugs me.
If I do
try
AForm.ShowModal
except
end;
the exceptions eventually raised in AForm
On Fri, 13 Dec 2019, Luca Olivetti via lazarus wrote:
Hello,
I don't remember if I asked this previously, but it always bugs me.
If I do
try
AForm.ShowModal
except
end;
the exceptions eventually raised in AForm aren't caught by the above
try..except, they always show the
Hello,
I don't remember if I asked this previously, but it always bugs me.
If I do
try
AForm.ShowModal
except
end;
the exceptions eventually raised in AForm aren't caught by the above
try..except, they always show the default error dialog.
I have to use Application.OnException to
14 matches
Mail list logo
